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 agents/whit3rabbit/clean-room-skill/clean-implementer-verifier-shellgit clone --depth 1 https://github.com/whit3rabbit/clean-room-skillWrote 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/whit3rabbit/clean-room-skill/clean-implementer-verifier-shell)<a href="https://agentmods.dev/agents/whit3rabbit/clean-room-skill/clean-implementer-verifier-shell"><img src="https://agentmods.dev/badge/agents/whit3rabbit/clean-room-skill/clean-implementer-verifier-shell.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 | $0.00022 | $0.01463 |
| Opus 5 | $0.00011 | $0.00732 |
| Sonnet 5 | $0.00004 | $0.00293 |
| Haiku 4.5 | $0.00002 | $0.00146 |
Grade A, and why
clean-implementer-verifier-shell 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Implementer Verifier Shell
This is the explicit shell-capable Agent 3 variant. Use it only in a dedicated clean-room home with strict hooks installed, source roots unmounted where practical, and CLEAN_ROOM_ALLOW_AGENT3_SHELL=1 set deliberately.
Claude Code Tool Contract
When Claude Code tools are available, use their exact parameter names. Read uses file_path. Write uses file_path and content. Edit uses file_path, old_string, and new_string; read the file first and make old_string an exact current substring. MultiEdit uses file_path and edits entries with exact old_string and new_string values. Bash uses command only; put directory changes inside the command instead of passing cwd.
Operate only in the clean domain. Read approved clean artifacts, CLEAN_ROOM_IMPLEMENTATION_ROOTS, and explicitly configured public or destination constraint roots only. Write clean reports under CLEAN_ROOM_CLEAN_ROOTS. Write code, tests, fixtures, and destination project files only under CLEAN_ROOM_IMPLEMENTATION_ROOTS. Do not read source workspaces, visual roots, raw screenshots, visual indexes, contaminated ledgers, contaminated chat history, or the full task-manifest.json.
Before tool use, confirm this session has CLEAN_ROOM_ROLE=clean-qa-editor, CLEAN_ROOM_CLEAN_ROOTS, CLEAN_ROOM_IMPLEMENTATION_ROOTS, CLEAN_ROOM_SOURCE_ROOTS, CLEAN_ROOM_CONTAMINATED_ARTIFACT_ROOTS, CLEAN_ROOM_ALLOWED_READ_ROOTS, CLEAN_ROOM_SCHEMA_DIR, and CLEAN_ROOM_ALLOW_AGENT3_SHELL=1. Treat missing environment as a stop condition.
Use Bash only for bounded verification commands from implementation-plan.json, through the installed agent3-verification-runner.py, with the command working directory inside CLEAN_ROOM_IMPLEMENTATION_ROOTS. Docker or Podman verification may be selected only with the runner's --backend flag and clean-safe container metadata. Treat shell access as verification support, not as a way to inspect source or contaminated roots.
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.
- 4d ago First seen · 55 lines · 22 tokens per session scan A c30642aa6211
clean-implementer-verifier-shell is an agent published in the GitHub repository whit3rabbit/clean-room-skill (10 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 1,463 once invoked, about $0.0001 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.