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/agentic-development/adev-plugin/codehealthnpx skills add agentic-development/adev-plugin --skill codehealthgit clone --depth 1 https://github.com/agentic-development/adev-pluginWhat 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.00092 | $0.04130 |
| Opus 5 | $0.00046 | $0.02065 |
| Sonnet 5 | $0.00018 | $0.00826 |
| Haiku 4.5 | $0.00009 | $0.00413 |
Grade A, and why
adev:codehealth 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 2d 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 — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Health Scanner
Scan source code for dead exports, orphan files, unused dependencies, stale code, and duplicate logic. Produces a severity-tiered markdown report from /adev:repomap artifacts.
Announce at start: "I'm using the adev:codehealth skill to scan for code health issues."
Arguments
| Argument | Required | Description |
|---|---|---|
| (none) | — | Full scan: all passes against all hygiene.source_roots |
--module <slug> |
No | Restrict scan to a single manifest module's paths |
--check <name> |
No | Comma-separated check filter. Valid: dead-exports, orphan-files, unused-deps, stale-code, duplicate-logic |
Both --module and --check may be combined (intersection: only named checks, only files in the module).
Prerequisites
Complete these checks in order. Stop at the first failure.
1. Manifest Validation
Read .context-index/manifest.yaml. If missing or unreadable:
INVALID_MANIFEST: Missing or invalid manifest.yaml —
source_rootsis required for codehealth scanning.
Verify hygiene.source_roots exists and is a non-empty list. If absent:
INVALID_MANIFEST: manifest.yaml is missing
hygiene.source_roots— required for codehealth scanning.
2. Repomap Artifact Validation
Check that both files exist:
.context-index/hygiene/symbol-ranks.json.context-index/hygiene/dependency-graph.json
If either is missing:
MISSING_REPOMAP: Repomap artifacts not found. Run
/adev:repomapfirst to generate the symbol index and dependency graph.
Stop without running any passes.
3. Argument Validation
If --module <slug> is provided, resolve against manifest.yaml modules[].slug. If not found:
UNKNOWN_MODULE: Unknown module '
<slug>'. Available modules:<comma-separated list of slugs>.
If --check <name> is provided, validate each name against the allowlist: dead-exports, orphan-files, unused-deps, stale-code, duplicate-logic. If any is unrecognized:
What ships with it
1 file 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.
- 2d ago First seen · 342 lines · 92 tokens per session scan A 0c98baaf83d6
adev:codehealth is a skill published in the GitHub repository agentic-development/adev-plugin (11 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 4,130 once invoked, about $0.0005 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…