A health-check feature for generated agent instructions that compares them with the current source code. It checks freshness, coverage, central files, and signs that the documentation has drifted.

Use it to check Claude and Codex project context, inspect documentation gaps, interpret the results, and rerun synchronization when repairs are needed.

Agent instructions can become outdated as a codebase changes. This shows where the context no longer matches the code and can offer repairs.

doc-impact — Skill by aspenkit

Install

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.

agentmods

npx agentmods add skills/aspenkit/aspens/doc-impact

Any agent

npx skills add aspenkit/aspens --skill doc-impact

Clone the repo

git clone --depth 1 https://github.com/aspenkit/aspens

Made for: Claude Code, Codex.

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,268 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00032	$0.01268
Opus 5	$0.00016	$0.00634
Sonnet 5	$0.00006	$0.00254
Haiku 4.5	$0.00003	$0.00127

Measured 3d ago against content hash 26cff4bad863, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

doc-impact 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 3d 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.

.agents/skills/doc-impact/SKILL.md · 55 lines

How it starts

The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are working on doc impact — the command that shows whether generated agent context is keeping up with the codebase, optionally interprets results via LLM, and can interactively apply recommended repairs.

Domain purpose

Audits the agent context generated by aspens against the live source tree, reports per-target health (Claude, Codex), and offers an interactive --apply flow that re-runs the right aspens doc init/sync variant to repair gaps. The LLM interpretation is a thin layer on top of deterministic metrics — the metrics are the contract.

Business rules / invariants

Target inference: If .aspens.json is absent, targets are inferred from scan results (.claude/ → claude, .agents/ → codex). Falls back to ['claude'].
LLM is optional and tool-less. Runs only when a CLI backend is detected. runLLM is invoked with disableTools: true; prompt must return pure JSON (bottom_line, improves, risks, next_step). Failure is caught and reported as "Analysis unavailable" — never fatal.
Graph failure is non-fatal. If buildRepoGraph throws (or --no-graph is passed), graph is null and hub coverage is skipped/n/a.
Hub coverage haystack is the code-map, not AGENTS.md. Post-Phase 1, ## Key Files no longer lives in root instructions. computeHubCoverage reads .claude/code-map.md (claude) or .agents/skills/architecture/references/code-map.md (codex). If the code-map file is missing, it reports codeMapMissing: true instead of spurious "missing hub" warnings. Older callers without repoPath fall back to the legacy contextText haystack.
Health score deductions (start 100): missing instructions −35; no skills −25; domain gaps proportional up to −25; missed hubs −4 each; drift −3 per file (cap −20); unhealthy hooks −10 (hook-capable targets only); broken save-tokens −5 (claude only).
LOW_SIGNAL_DOMAIN_NAMES (config, test, tests, __tests__, spec, e2e) are excluded from coverage scoring but tracked in excluded.
SOURCE_EXTS extends the scanner set with .scala, .clj, .elm, .vue, .svelte for drift detection. Adding a language for drift requires updating this set.
Walk depth capped at 5 — deep nested source files won't appear in drift analysis.

Read the full file on GitHub · 55 lines

Changes

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.

3d ago First seen · 55 lines · 32 tokens per session scan A 26cff4bad863

Subscribe to this mod's changes

doc-impact is a skill published in the GitHub repository aspenkit/aspens (96 stars, last pushed 18d ago), licensed MIT. It adds 32 tokens to every session and 1,268 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-30.

Building agents ai-agents claude-code cli codebase-analysis developer-tools documentation

golden-rss

Use when testing the rss golden build.

yusufkaraaslan/Skill_Seekers · 12 tokens

architectural-decisions

Use when encountering questions about WHY code is built a certain way, when about to make architectural changes (new patterns, restructuring, choosing between approaches), or when the user asks about design rationale in a Repowise-indexed codebase (.repowise/ directory exists). Also activates when commit messages or…

repowise-dev/repowise · 87 tokens

pre-modification-check

Use before modifying, refactoring, moving, or deleting files in a Repowise-indexed repository, especially shared utilities, core modules, public APIs, or files the user did not explicitly identify.

repowise-dev/repowise · 45 tokens

automated-test-planning

Produce a standalone test plan by analyzing code for test coverage gaps and edge cases. Use when you need to create, generate, or draft a test plan for a branch, need to analyze test coverage, or need to identify what tests to write for specific files or directories. Does not produce a plain-language plan for a person…

testdouble/han · 146 tokens

code-overview-to-confluence

Produces a progressive-disclosure overview of unfamiliar code or a pull request's changes with code-overview and publishes the resulting overview to a user-specified Confluence location. Use when the user wants code or a PR explained, oriented, or made sense of AND the overview posted to a Confluence space or page.…

testdouble/han · 179 tokens

project-documentation-to-confluence

Creates or updates project documentation for a feature, system, or component and publishes it to a user-specified Confluence location. Use when the user wants feature or system documentation written to Confluence, posted to a Confluence space or page, or synced to a Confluence location. Requires a configured Atlassian…

testdouble/han · 159 tokens