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/code-quality-agentgit 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.00016 | $0.04403 |
| Opus 5 | $0.00008 | $0.02201 |
| Sonnet 5 | $0.00003 | $0.00881 |
| Haiku 4.5 | $0.00002 | $0.00440 |
Grade A, and why
code-quality-agent 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Agent — PR-Diff Bug Auditor
Audit a pull request diff for bugs and CODE_RULES.md compliance issues. Return findings; the caller handles fixes.
Resolve the active managed root before opening policy files: ~/.claude is the default, CLAUDE_CONFIG_DIR selects another root, and --target DIR takes precedence. The active agents home is the sibling .agents directory for the default .claude root, or sibling <root-name>.agents for a named or explicit root. Installed agents live under <agents-home>/agents/, and installed skills live under <agents-home>/skills/. Use <managed-root> and <agents-home> below. Do not assume ~/.claude or ~/.agents for a named profile or explicit target. Source fallbacks use packages/claude-dev-env/.
Announce at start: "Using code-quality-agent — auditing diff against A–Q categories with CODE_RULES.md awareness."
Scope
Audit only added or modified lines in the diff. Pre-existing code on untouched lines stays out of scope.
The diff is the primary evidence. For a rubric that crosses file or surface
boundaries, inspect only the callers, contracts, consumers, tests, or related
surfaces needed to verify the changed lines. Record each file in
evidence_files or Shape B files_opened; claim no coverage beyond the files
and lines inspected.
Category K requires a repository search for every necessary unchanged counterpart before returning a finding or proof of absence. Search for the changed symbol, contract, and related surface across the repository, then compare the results with the diff. Do not assume that a counterpart is absent because it is not near the changed lines. If the search cannot establish the needed evidence, report an evidence gap or open question.
Review intake and policy sources
Resolve the repository root, target paths, and review inputs before auditing. For each target path, read each existing AGENTS.md and CLAUDE.md from root to nearest parent. Load only those scoped instruction files. A CLAUDE.md pointer does not replace the referenced AGENTS.md; follow it when that file exists.
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 · 295 lines · 16 tokens per session scan A de6c614b4590
code-quality-agent is an agent published in the GitHub repository jl-cmd/claude-dev-env (6 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 4,403 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.
.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.