Borrowing it
Nothing to install: this file belongs to rex/mcp-rancher. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rex/mcp-rancher/main/.claude/commands/retrofit.mdgit clone --depth 1 https://github.com/rex/mcp-rancherWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/rex/mcp-rancher/retrofit)<a href="https://agentmods.dev/commands/rex/mcp-rancher/retrofit"><img src="https://agentmods.dev/badge/commands/rex/mcp-rancher/retrofit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/rex/mcp-rancher/retrofit"><img src="https://agentmods.dev/badge/commands/rex/mcp-rancher/retrofit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00017 | $0.02733 |
| Opus 5 | $0.00009 | $0.01367 |
| Sonnet 5 | $0.00003 | $0.00547 |
| Haiku 4.5 | $0.00002 | $0.00273 |
Grade C, and why
retrofit scanned grade C with 1 finding 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 6d ago.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
description mentioning `rm -rf /`). Workaround: Copies of this mod
1 near-identical copy found in the catalogue:
- retrofit — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/retrofit — brownfield agent-readiness retrofit
This command runs the 5-PR brownfield sequence top-to-bottom. The user invoking it IS the consent — proceed without any "are we doing this?" check. Each PR is one commit; each commit pushes immediately.
Step 0 — Detect git environment
Before applying any PR, detect the working tree's shape. Each PR's
CHECKLIST starts with git checkout -b chore/... — that fails if
this is a worktree, detached HEAD, or trunk-strategy repo.
git rev-parse --is-inside-work-tree 2>/dev/null # is this a git repo?
git symbolic-ref --short HEAD 2>/dev/null # current branch (empty = detached)
git worktree list 2>/dev/null # main checkout vs worktree?
git config --get remote.origin.url 2>/dev/null # remote URL (empty = no remote)
test -f VIBE.yaml && grep -E '^\s*branch_strategy:' VIBE.yaml # trunk vs feature-branch?
What to do with each signal:
- Detached HEAD or worktree: skip the
git checkout -bstep in every CHECKLIST. Push withgit push origin HEAD:<trunk>(where<trunk>is the trunk branch — usuallymain, sometimesmaster). branch_strategy: trunkin VIBE.yaml: also skipgit checkout -b. Commit directly on the current branch and push.- No remote: push steps no-op silently. Surface that and ask the user to add a remote, or proceed without push.
If everything is normal (attached HEAD, single checkout, no trunk strategy), follow each CHECKLIST verbatim.
Step 1 — Discovery (minimal — most answers come from the repo)
Read what's already there before asking anything:
git log --oneline -20 # context for recent activity
ls -la # top-level layout
cat README.md # stated purpose (or AGENTS.md if present)
test -f pyproject.toml && echo python # stack signal
test -f package.json && echo typescript # stack signal
test -f Cargo.toml && echo rust # stack signal
test -f go.mod && echo go # stack signal
test -f VIBE.yaml && cat VIBE.yaml # existing repo policy
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.
- 6d ago Changed · -33 lines a852d757151b
- 10d ago First seen · 270 lines · 17 tokens per session scan C d3f5d634b1c5
retrofit is a command published in the GitHub repository rex/mcp-rancher (1 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 2,733 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
fix
Universal debugging and fix application with semantic code analysis.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
design
A command that turns an existing plan into a detailed technical design for building the feature.
p3-ux-wireframes
Creates wireframes (ASCII art) for the most important screens with interaction descriptions.