Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
/plugin marketplace add rlx/uplevelnpx agentmods add plugins/rlx/uplevel/marketplacegit clone --depth 1 https://github.com/rlx/uplevelGrade A, and why
uplevel scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "uplevel",
"description": "The uplevel skill, installable as a plugin.",
"owner": {
"name": "Lior Rudnik and Tracey Mercer"
},
"plugins": [
{
"name": "uplevel",
"description": "Finds the engineering controls your repository does not have — CI that never runs on pull requests, a check target that quietly rewrites files, a migration with nothing in front of it — and hands back a numbered plan. Advisory: it changes nothing until you pick.",
"source": "./",
"category": "development",
"homepage": "https://github.com/rlx/uplevel"
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 18 lines scan A 6779ba7fab5c
uplevel is a plugin published in the GitHub repository rlx/uplevel (3 stars, last pushed 7d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other plugins, from other repositories
marketplace
SwiftUI workflow audit — find dead ends, broken promises, and UX friction.
workflow-audit
SwiftUI workflow audit — find dead ends, broken promises, and UX friction. Bundled with a phased plan generator.
skill-reviewer
Use when reviewing a Claude Code skill, auditing skill quality before publish, or asking "is this skill any good?". Produces structured reports with file:line citations, severity-rated findings cards, and an optional second-opinion pass. Lens variants: full (default), safety, discoverability, architecture…
skill-reviewer
Use when reviewing a Claude Code skill, auditing skill quality before publish, or asking "is this skill any good?". Produces structured reports with file:line citations, severity-rated findings cards, and an optional second-opinion pass. Lens variants: full (default), safety, discoverability, architecture…
radar-suite
Six-skill audit suite for iOS/Swift codebases with 3-axis classification framework.
radar-suite
Six-skill audit suite for iOS/Swift codebases: data models, UI paths, data round-trips, time bombs, visual quality, and capstone grading. As of v2.0 every finding is classified on a 3-axis framework (real bug / scatter / dead code) with mandatory coaching citations to patterns in the audited codebase.