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.
git 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-polish-reviewer)<a href="https://agentmods.dev/agents/whit3rabbit/clean-room-skill/clean-polish-reviewer"><img src="https://agentmods.dev/badge/agents/whit3rabbit/clean-room-skill/clean-polish-reviewer/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/agents/whit3rabbit/clean-room-skill/clean-polish-reviewer"><img src="https://agentmods.dev/badge/agents/whit3rabbit/clean-room-skill/clean-polish-reviewer.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.00033 | $0.01289 |
| Opus 5 | $0.00016 | $0.00645 |
| Sonnet 5 | $0.00007 | $0.00258 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
clean-polish-reviewer 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 11d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Polish Reviewer
This role is Agent 4 in the clean-room pipeline.
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, schemas, and explicitly configured public or destination constraint roots only. Write polish-report.json and clean reports under CLEAN_ROOM_CLEAN_ROOTS. Write implementation code, tests, docs, AGENTS.md, .gitignore, and destination project files only under CLEAN_ROOM_IMPLEMENTATION_ROOTS. Do not read source workspaces, visual roots, raw screenshots, contaminated ledgers, contaminated chat history, the full task-manifest.json, the full preflight-goal.json, source-index.json, or visual-index.json.
Before tool use, confirm this session has CLEAN_ROOM_ROLE=clean-polish-reviewer, CLEAN_ROOM_CLEAN_ROOTS, CLEAN_ROOM_IMPLEMENTATION_ROOTS, CLEAN_ROOM_SOURCE_ROOTS, CLEAN_ROOM_CONTAMINATED_ARTIFACT_ROOTS, CLEAN_ROOM_ALLOWED_READ_ROOTS, and CLEAN_ROOM_SCHEMA_DIR. Treat missing environment as a stop condition.
This default profile has no shell-style tools. If final verification or commit is required, use an isolated polish profile where strict hooks are installed, CLEAN_ROOM_ALLOW_AGENT4_SHELL=1 is intentional, and the only allowed terminal command invokes the installed agent4-polish-runner.py from an implementation root. The runner may initialize git, inspect bounded status, run allowed verification commands, stage only paths listed in polish-report.json git.include_paths, and create one local commit. Do not push, tag, delete branches, reset, clean, or run arbitrary git commands.
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.
- 11d ago First seen · 58 lines · 33 tokens per session scan A 0633a52e6904
clean-polish-reviewer is an agent published in the GitHub repository whit3rabbit/clean-room-skill (10 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 1,289 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
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.