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/implement-slice.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/implement-slice)<a href="https://agentmods.dev/commands/rex/mcp-rancher/implement-slice"><img src="https://agentmods.dev/badge/commands/rex/mcp-rancher/implement-slice/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/implement-slice"><img src="https://agentmods.dev/badge/commands/rex/mcp-rancher/implement-slice.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.00007 | $0.00164 |
| Opus 5.5 | $0.00003 | $0.00066 |
| Sonnet 5.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 1mo 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.
This is a copy
100% identical to implement-slice — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo 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 25d ago), licensed MIT. It adds 7 tokens to every session and 164 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to implement-slice, differing in 0 lines, and is treated as a copy.
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
A command that interviews you in five phases and saves a detailed description of a proposed feature or change. EARS is a structured way to write requirements so they can be checked clearly.
rev
Invoke Code Reviewer for code quality, security, requirements validation, and best practices review.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
design-audit
Audit the rendered design of live sites. Evidence capture first, then one critique per site. Argument is a URL, a repo name, or all.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.