Borrowing it
Nothing to install: this file belongs to aspenkit/aspens. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aspenkit/aspens/main/.agents/skills/doc-impact/SKILL.mdgit clone --depth 1 https://github.com/aspenkit/aspensWrote 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/aspenkit/aspens/doc-impact)<a href="https://agentmods.dev/skills/aspenkit/aspens/doc-impact"><img src="https://agentmods.dev/badge/skills/aspenkit/aspens/doc-impact/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aspenkit/aspens/doc-impact"><img src="https://agentmods.dev/badge/skills/aspenkit/aspens/doc-impact.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00032 | $0.01268 |
| Opus 5.5 | $0.00013 | $0.00507 |
| Sonnet 5.5 | $0.00006 | $0.00254 |
| Haiku 4.5 | $0.00003 | $0.00127 |
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 1mo 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 — 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.jsonis 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.
runLLMis invoked withdisableTools: 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
buildRepoGraphthrows (or--no-graphis passed),graphisnulland hub coverage is skipped/n/a. - Hub coverage haystack is the code-map, not AGENTS.md. Post-Phase 1,
## Key Filesno longer lives in root instructions.computeHubCoveragereads.claude/code-map.md(claude) or.agents/skills/architecture/references/code-map.md(codex). If the code-map file is missing, it reportscodeMapMissing: trueinstead of spurious "missing hub" warnings. Older callers withoutrepoPathfall back to the legacycontextTexthaystack. - 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 inexcluded.SOURCE_EXTSextends the scanner set with.scala,.clj,.elm,.vue,.sveltefor 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.
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.
- 1mo ago First seen · 55 lines · 32 tokens per session scan A 26cff4bad863
doc-impact is a skill published in the GitHub repository aspenkit/aspens (103 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 1,268 once invoked, about $0.0001 per session on Opus 5.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
do
Work a SpecWeave increment task by task - claim, implement inside its Files, test, commit, done with evidence - alone, unattended or in lanes, then close. Use for "implement", "continue", "auto".
handoff
Hand work to another tool, account or machine and pick it up there, in two words. Use when the user says "hand off", "hand off all", "out of tokens", "switching accounts", "pick up" or "continue".
sw-do
Work a SpecWeave increment task by task - claim, implement inside its Files, test, commit, done with evidence - alone, unattended or in lanes, then close. Use for "implement", "continue", "auto".
sw-handoff
Hand work to another tool, account or machine and pick it up there, in two words. Use when the user says "hand off", "hand off all", "out of tokens", "switching accounts", "pick up" or "continue".
increment
Plan work as a SpecWeave increment - one spec.md with Problem, Scope, numbered ACs, Approach and Tasks - before writing code. Use for "plan a feature", "new increment", "let's build X".
review
Adversarial review of an increment before it ships, by a fresh context or another model family; every finding cites path:line and is re-verified. Use for "review", "qa", "critique this".