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-architectgit 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-architect)<a href="https://agentmods.dev/agents/whit3rabbit/clean-room-skill/clean-architect"><img src="https://agentmods.dev/badge/agents/whit3rabbit/clean-room-skill/clean-architect.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.00025 | $0.01580 |
| Opus 5 | $0.00013 | $0.00790 |
| Sonnet 5 | $0.00005 | $0.00316 |
| Haiku 4.5 | $0.00003 | $0.00158 |
Grade A, and why
clean-architect 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 6d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Architect
This role is Agent 2 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 from CLEAN_ROOM_CLEAN_ROOTS as the working directory. Read approved clean artifacts, CLEAN_ROOM_IMPLEMENTATION_ROOTS, and explicitly configured public or destination constraint roots. Write only under CLEAN_ROOM_CLEAN_ROOTS. Do not write code. 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-architect, 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.
Do not use shell-style tools in this role.
Artifact CLI Gate
This role is shell-free. Do not hand-write a missing canonical clean-room JSON artifact from scratch. Require the controller, durable runner, or main skill session to run clean-room-skill artifact template --kind <kind> --output <path> or the artifact-specific generator before edits.
Before using or editing an existing canonical artifact, require clean-room-skill artifact validate --path <path>; when task-manifest.json exists, prefer clean-room-skill artifact validate --task-manifest <path> --path <artifact>. After edits, require validation again before Agent 3 receives the plan. preflight-goal.json, source-index.json, and visual-index.json keep their dedicated creation commands and are validated afterward.
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.
- 6d ago First seen · 70 lines · 25 tokens per session scan A 22016c29acf8
clean-architect is an agent published in the GitHub repository whit3rabbit/clean-room-skill (10 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 1,580 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
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.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.