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/ahepi/deepreason/dr-audit-deadnpx skills add AHepi/DeepReason --skill dr-audit-deadgit clone --depth 1 https://github.com/AHepi/DeepReasonWrote 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/ahepi/deepreason/dr-audit-dead)<a href="https://agentmods.dev/skills/ahepi/deepreason/dr-audit-dead"><img src="https://agentmods.dev/badge/skills/ahepi/deepreason/dr-audit-dead.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.00052 | $0.00851 |
| Opus 5 | $0.00026 | $0.00426 |
| Sonnet 5 | $0.00010 | $0.00170 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
dr-audit-dead 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 5d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit: dead code
Entry: LEDGER.md exists; dead.md missing or contains a package
row marked pending. Exit for one invocation: ONE package's census
complete, its row flipped to done. The router re-invokes until no
pending rows remain (S1: the loop lives in the router).
On first invocation, write the package list into dead.md:
ls -d src/deepreason/*/ src/deepreason/*.py, one row each, all
pending.
Operations (for the next pending package P)
- Symbol census:
rg -n '^(def|class) [A-Za-z_]' <P> --type py > proof/dead-<P>-symbols.txt - For each symbol NAME, count referencing files outside its defining
file:
rg -l -w 'NAME' src/ tests/ scripts/ tools/ | grep -v <defining-file>Hits ≥ 1 → verdictreferenced(no LEDGER row; tally only). Hits = 0 → step 2b. 2b. Intra-file use check (a symbol called only from its own file is wired, not dead):rg -c -w 'NAME' <defining-file>Count ≥ 2 (the definition line plus at least one use) → verdictreferenced, noteintra-file(tally only). Count = 1 → step 3. - String-reference scan (dynamic dispatch, registries, config
strings):
rg -l "['\"]NAME['\"]" src/ tests/ scripts/ tools/Hits ≥ 1 → verdictdynamic-ref, row it with the hit file (these are load-bearing but invisible to imports — worth a row, not a prompt). Hits = 0 → step 4. - Entry-point scan:
rg -l 'NAME' pyproject.toml. Hit → verdictentry-point. No hit → verdictcandidate-dead, row it, dispositionparked, both scan outputs saved toproof/dead-<id>.txt. - Append the package's tally line to
dead.md(P: S symbols, R referenced, D dynamic-ref, C candidate-dead) and flip its row todone.
GATE
Pass for the invocation: the package row is done, its tally line
exists, and every candidate-dead row cites a proof file containing
BOTH empty scans (G2 — "dead" is only sayable with the two searches
pasted). Verdict labels: referenced | dynamic-ref |
entry-point | candidate-dead.
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.
- 5d ago First seen · 71 lines · 52 tokens per session scan A 2e55409cc28b
dr-audit-dead is a skill published in the GitHub repository AHepi/DeepReason (141 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 851 once invoked, about $0.0003 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.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…