Universal Modder

Point Claude at any game. Skills, tools and the fal MCP that let Claude Code mod almost any PC game you own: recon, reverse engineering, fal-generated art/3D/audio, in-game testing, showcase videos.

Agent Skills Python Listed MIT

Is Universal Modder safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.6 / 10
Provenance None
Signed commits 100%
Last push today
Compare Universal Modder
Suggest a correction

In detail: Universal Modder scores 64.8/100 (Grade C), ranked #73 of 396 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.6/10; 100% of recent commits are signed; last pushed 2026-11-15. Every point is earned from checkable signals — never paid placement. How scoring works →

How Universal Modder could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Chain of custody

Scanners check what the code says. This traces who ships Universal Modder and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Signed

    github.com/rehan-remade/universal-modder, MIT, last pushed 2026-11-15. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.6/10 (scanned Oct 25, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review9
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies10
    All 18 Scorecard checks
    Binary-Artifacts 8
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 9
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 10
    SAST 0
    Security-Policy 4
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 10
  3. Published packages None

    No registry package. Universal Modder is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-10-15 OSSF Scorecard: 4.1/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Universal Modder’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Universal Modder compares in Agent Skills

  1. #71 Cloudflare Skills 64.9 +0.1
  2. #72 Lobehub 64.9 +0.1
  3. #73 Universal Modder 64.8 this agent
  4. #74 Html Anything 64.3 −0.5
  5. #75 Expo Skills 64.2 −0.6

Bars show each HVTrust score; the tick marks Universal Modder’s 64.8.

Where the 64.8 comes from

HVTrust dimensions vs the Agent Skills average

64.8 / 100 · 100.0% confidence

Universal Modder Agent Skills average (396 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.8 / 25
2.6 above avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.7 below avg 11.5
Transparency50% declared license · 50% OSSF Scorecard
12.4 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.0 above avg 14.0
AdoptionLog-scaled stars · package downloads
9.6 / 20
in line with avg 9.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.6/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent
View Agent Skills Report missing data
88.0
Activity sub-score · out of 100
#73

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-15 16:08 UTC · Repo last pushed today

Rank Trend

2026-10-09 2026-11-15

Activity & Reach

Stars
9.7k
Forks
1.1k
Last Push
2026-11-15
today
Commits (4 wk)
124
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
=
was #73

Analysis

Activity Inputs

88.0 / 100
StarsRepository reach
23.9 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.1 / 20

Common questions about Universal Modder

Universal Modder has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Universal Modder publish package provenance?
No published build provenance is currently detected for Universal Modder. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Universal Modder have an OpenSSF Scorecard?
Universal Modder has an OpenSSF Scorecard score of 4.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Universal Modder actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Universal Modder use?
Universal Modder ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Universal Modder's commits signed?
100% of the last 100 commits to Universal Modder are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Universal Modder appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Universal Modder?

For maintainers

HVTrust scores Universal Modder from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Listed 1HVTrust 1Rank 1Grade 1Scorecard 1
2026-10-15
Scorecard Added
OSSF Scorecard: 4.1/10
2026-10-15
Grade Changed
Trust grade D → C
2026-10-15
Rank Moved
Rank rose 293 spots (#362 → #69)
2026-10-15
HVTrust Changed
HVTrust up 35.5pts (28.0 → 63.5)
2026-10-09
Newly Listed
First tracked at rank #353

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 64.8 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/universal-modder.svg)](https://hvtracker.net/agents/universal-modder)
HTML:
<a href="https://hvtracker.net/agents/universal-modder"><img src="https://hvtracker.net/badge/universal-modder.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON