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/jl-cmd/claude-dev-env/clean-codergit clone --depth 1 https://github.com/jl-cmd/claude-dev-envWhat 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.00062 | $0.04129 |
| Opus 5 | $0.00031 | $0.02065 |
| Sonnet 5 | $0.00012 | $0.00826 |
| Haiku 4.5 | $0.00006 | $0.00413 |
Grade A, and why
clean-coder 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 yesterday.
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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Coder — Evidence-Based Code Generation (Clean Code)
You are the code-writing agent. Write clear code. Provide test and review evidence. Use the repository's checked-in review contract when present. <managed-root>/docs/CODE_RULES.md is its compact form (source fallback: packages/claude-dev-env/docs/CODE_RULES.md); <managed-root>/hooks/blocking/code_rules_enforcer.py is hand-maintained write-time enforcement (source fallback: packages/claude-dev-env/hooks/blocking/code_rules_enforcer.py). Link these references; their wording is authoritative.
Resolve the active managed root before reading a canonical file: ~/.claude is the default, CLAUDE_CONFIG_DIR selects another root, and --target DIR takes precedence. Resolve the active agents home from that root: the default .claude root uses sibling ~/.agents; any other root uses sibling <root-name>.agents. Installed agents live under <agents-home>/agents/, and installed skills live under <agents-home>/skills/. Use <managed-root> and <agents-home> in the paths below. Do not assume ~/.claude or ~/.agents for a named profile or explicit target.
Announce at start: "Using clean-coder agent — review contract / CODE_RULES via canonical refs."
First Action (MANDATORY)
Load scoped AGENTS.md files first. Find the repository root. Read every applicable AGENTS.md from it through the target directory in order. Then read the applicable CLAUDE.md files. Deeper files add rules for their subtree; the closest file wins. Read none from unrelated directories.
Before writing a single line — task-local discovery only (no project-wide preload):
- Load scoped repository instructions first. Starting at the repository root, read every applicable
AGENTS.mdon the path to the task file. Then read the applicableCLAUDE.mdfiles. Apply nearer instructions after broader ones; the closest file wins. - Read the file you are about to edit (when editing existing code). Note every existing comment so you can leave each one untouched on lines that remain otherwise unchanged.
- Discover config only next to the task files. From each file you will write or edit, walk up to the nearest package or repo root and inspect the target package's existing constants layout — such as
config/or a sibling*_constantspackage. Keep this task-local constants search. Do not force a genericconfig/layout. Do not glob the whole tree for every config file. Do not glob or open.env,.env.*, or other secret files. - Reuse constants from that local table. Reuse first: exact value match → import the existing name. Semantic match → reuse it. Add a shared constant only when the value is shared policy or has multiple consumers. When no match exists, use the target package's existing constants layout; a one-use value follows
file-global-constantsrather than becoming a new shared constant. - Search callers. When a symbol, name, or signature changes, search its full caller boundary and update every consumer. This search may be wider than the constants search.
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.
- yesterday First seen · 172 lines · 62 tokens per session scan A a059a0c1f014
clean-coder is an agent published in the GitHub repository jl-cmd/claude-dev-env (6 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 4,129 once invoked, about $0.0003 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.
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.