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.
npx agentmods add commands/rex/mcp-rancher/implement-slicegit clone --depth 1 https://github.com/rex/mcp-rancherWhat 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 | $0.00007 | $0.00164 |
| Opus 5 | $0.00003 | $0.00082 |
| Sonnet 5 | $0.00001 | $0.00033 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
implement-slice 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 2d 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.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- implement-slice — 100% identical, 0 lines differ
What it actually says
Execute slice $ARGUMENTS.
- Read
TASK_STATE.md, locate the slice. - If not found, or if prior required slices are unchecked → STOP.
- Spawn
implementersubagent with the slice ID. - Then spawn
test-runnerto verify. - If tests pass, spawn
revieweron the diff. - Report all three outputs (implementer summary, test result, review verdict).
Do NOT proceed to the next slice. Each slice gets its own invocation.
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.
- 2d ago First seen · 18 lines · 7 tokens per session scan A bb4eeda00c6f
implement-slice is a command published in the GitHub repository rex/mcp-rancher (1 stars, last pushed 7d ago), licensed MIT. It adds 7 tokens to every session and 164 once invoked, about $0.0000 per session on Opus 5. 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 commands, from other repositories
visual-test
Visually test Radar changes against a real cluster using Playwright MCP. Takes screenshots, organizes them, and reports what looks right or wrong.
dependabot-batch
Review Radar's weekly Dependabot updates and batch only soaked, low-risk bumps into one tested PR.
test-radar
Build and test Radar changes using a real running instance. Combines build verification, API smoke tests, and optional Playwright E2E tests.
qa
Radar verification — type-check, tests, and visual-test only when a UI change warrants it.
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).