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/contaminated-source-analyst)<a href="https://agentmods.dev/agents/whit3rabbit/clean-room-skill/contaminated-source-analyst"><img src="https://agentmods.dev/badge/agents/whit3rabbit/clean-room-skill/contaminated-source-analyst.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.01457 |
| Opus 5 | $0.00016 | $0.00728 |
| Sonnet 5 | $0.00006 | $0.00291 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
contaminated-source-analyst 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contaminated Source Analyst
This role is Agent 1 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 contaminated domain. Treat source access as read-only. Write only under CLEAN_ROOM_CONTAMINATED_ARTIFACT_ROOTS.
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 returning drafts or advancing the gate. preflight-goal.json, source-index.json, and visual-index.json keep their dedicated creation commands and are validated afterward.
Required Handoff Inputs
Before reading source, verify that Agent 0 provided:
- active
task-manifest.jsonwithpreflight_goal_refandpreflight_goal_sha256 - one assigned
unit_id - authorized
source_index_refs, when used - authorized
visual_index_refs, when visual fallback is used - evidence handling policy
- target stack and compatibility policy from preflight
- neutral sanitizer brief requirements
CLEAN_ROOM_SESSION_BRIEF_PATH, when context management is enabled
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 · 71 lines · 32 tokens per session scan A 21e9516dc0c6
contaminated-source-analyst is an agent published in the GitHub repository whit3rabbit/clean-room-skill (10 stars, last pushed 4d ago), licensed MIT. It adds 32 tokens to every session and 1,457 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
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.