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 skills/darrencroton/ai-agent-coder/code-healthnpx skills add darrencroton/ai-agent-coder --skill code-healthgit clone --depth 1 https://github.com/darrencroton/ai-agent-coderWrote 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/skills/darrencroton/ai-agent-coder/code-health)<a href="https://agentmods.dev/skills/darrencroton/ai-agent-coder/code-health"><img src="https://agentmods.dev/badge/skills/darrencroton/ai-agent-coder/code-health.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 | $0.00075 | $0.01494 |
| Opus 5 | $0.00037 | $0.00747 |
| Sonnet 5 | $0.00015 | $0.00299 |
| Haiku 4.5 | $0.00007 | $0.00149 |
Grade A, and why
code-health 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Health
Measure first; interpret second. The analyzer locates structural evidence and quantifies change. The agent then reads the implicated code to decide whether the structure is justified. A metric is never itself a defect.
This skill complements lint: lint owns mechanically decidable local defects, while code-health owns measured signals that require contextual judgment. It is not a quality gate and never emits an unhealthy verdict.
Invariants
- Differential by default. Compare with the change's starting ref. Attribute only raw-value changes and new structural relationships to the change; retain whole-repository values as context. Use
--allonly for an explicit baseline audit. - Facts and judgment stay separate. The script emits facts, coverage, and bounded investigation candidates. The agent supplies interpretation and recommendations after inspecting the code.
- Missing measurement is unavailable, never clean. Read the language-by-metric coverage matrix before interpreting results. Never compare measured Python functions with unmeasured functions in another language. Read
repository.unrecognised_extensionstoo — a language absent from the extension table produces no coverage row, so that grouped extension-to-count map is the only evidence those files exist — andrepository.coverage_limitsfor what the measurement could not reach. - No score or universal target. Do not convert comments-to-code, tests-to-code, duplication, complexity, or any composite into a repository grade. Ratios and ranks identify anomalies; they do not define quality.
- Raw change, not percentile movement. A candidate must be supported by a changed raw value or new relationship. Population rank may order a bounded reading list but never establishes regression.
- Git defines the default scope. Analyze tracked and untracked non-ignored files. Apply no hidden vendor/generated exclusions. Record every explicit configuration exclusion.
- Successful analysis exits zero regardless of evidence. Exit
2means an execution error; exit3means required coverage was unavailable or a differential scope was empty. No exit code means "unhealthy." - No installation at all. The portable floor requires only Python 3.13 and Git. Lizard is the optional multi-language complexity collector:
detectreports whether it is present and names the command that would install it. The analyzer has no code path that installs anything, so widening coverage is always a human's explicit act outside this skill.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed 85685481051d
- 5d ago First seen · 78 lines · 75 tokens per session scan A b93525cecf63
code-health is a skill published in the GitHub repository darrencroton/ai-agent-coder (2 stars, last pushed 3d ago), licensed MIT. It adds 75 tokens to every session and 1,494 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…