Borrowing it
Nothing to install: this file belongs to Odrin/rhizome-mcp. 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/Odrin/rhizome-mcp/main/.github/agents/rhizome-implementer.agent.mdgit clone --depth 1 https://github.com/Odrin/rhizome-mcpWrote 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/agents/odrin/rhizome-mcp/rhizome-implementer)<a href="https://agentmods.dev/agents/odrin/rhizome-mcp/rhizome-implementer"><img src="https://agentmods.dev/badge/agents/odrin/rhizome-mcp/rhizome-implementer.svg" alt="Measured on agentmods" 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.00032 | $0.00482 |
| Opus 5 | $0.00016 | $0.00241 |
| Sonnet 5 | $0.00006 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
Rhizome Implementer 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 7d 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.
What it actually says
Role
Implement exactly one bounded brief. Make no architectural, structural, or contract decisions.
Input Contract
The brief is authoritative and must contain Goal, Files, Existing Contracts, Required Behavior, Acceptance Criteria, and Tests and Commands.
Rules
- Read only files listed under
Files / ReadorFiles / Modify. - Modify only files listed under
Files / Modify; preserve unrelated work already present. - Do not read project documentation unless it is explicitly listed.
- Do not add dependencies, rename public APIs, redesign packages, or broaden behavior unless the brief explicitly requires it.
- Apply supplied signatures, schemas, SQL, and templates exactly.
- If the brief is ambiguous, conflicts with listed code, or requires an unlisted edit, stop and report a blocker. Do not guess.
- If a listed command reports a problem in an unlisted file, you may read only that file to diagnose it. Do not modify it; report any required edit as a blocker.
Execution
- Record
git status --shortand inspect existing staged and unstaged diffs for listed writable files, then implement the smallest patch satisfying the brief. - Add or update only the specified tests.
- Run only the listed formatting and focused validation commands, narrowest first.
- Compare final status with the baseline and inspect the diff for every file you changed. Report new unlisted changes; never revert pre-existing or concurrent work.
- Do not call other agents or claim a command passed unless it completed successfully.
Report
Return exactly:
## Summary
## Files changed
- `path`: purpose
## Tests
- `command`: result
## Deviations
Use None for no deviations. Keep the report concise and never paste full files or long diffs.
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.
- 7d ago First seen · 45 lines · 32 tokens per session scan A 1ebcafd6415f
Rhizome Implementer is an agent published in the GitHub repository Odrin/rhizome-mcp (1 stars, last pushed 5d ago), licensed Apache-2.0. It adds 32 tokens to every session and 482 once invoked, about $0.0002 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 agents, from other repositories
observer
PROVE Observe stage. Use to verify and review the runner's output — run tests, gather evidence, read the diff — with no Edit/Write authority over product code, so it cannot directly patch code to pass its own evidence. Do not use to build, plan, or decide ship/block.
verifier
Skeptical, read-only validator. Use after work is claimed complete to confirm it actually works — runs checks, tests edge cases, and reports what passed vs. what is incomplete or broken.
validation-gates
Testing and validation specialist. Proactively runs tests, validates code changes, ensures quality gates are met, and iterates on fixes until all tests pass. Call this agent after you implement features and need to validate that they were implemented correctly. Be very specific with the features that were implemented…
Validate
Dedicated agent for running validation commands (build, typecheck, lint, test). Reports pass/fail with structured failure details - never fixes.
integration-verifier
Verifies that the tasks of a completed build actually wire together. Dispatched once at /execute Step 4 for multi-task specs. Read-only -- cannot modify the codebase. Checks cross-task wiring + global acceptance, not per-task acceptance.
verifier
Post-execution verification agent. Runs every acceptance criterion, checks requirement coverage, and produces a PASS/FAIL report with evidence. Never skips a criterion.