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-brokennpx skills add AHepi/DeepReason --skill dr-audit-brokengit 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-broken)<a href="https://agentmods.dev/skills/ahepi/deepreason/dr-audit-broken"><img src="https://agentmods.dev/badge/skills/ahepi/deepreason/dr-audit-broken.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.00044 | $0.00715 |
| Opus 5 | $0.00022 | $0.00358 |
| Sonnet 5 | $0.00009 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
dr-audit-broken 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit: broken code
Entry: LEDGER.md exists, broken.md missing. Exit: broken.md
written, LEDGER rows added, proofs in proof/.
Broken means: an instrument's output moved from
docs/AUDIT_BASELINES.md §Instruments. The instruments define
broken; this worker adds no judgment of its own (G3).
Operations
pip install -e . --break-system-packages -qandpip install pytest pytest-xdist jsonschema --break-system-packages -q. Run every command below withpython -mwhere applicable; save each full output toproof/broken-<n>.txt.python -m pytest tests/ -q -n 4— compare failures to the baseline failure list. Re-run any non-baseline failure serially (python -m pytest <nodeid> -q) before rowing it: still red → verdictbroken; green serially → verdictflaky(row it; flaky is a finding unless baseline-listed).python tools/docs_verify.py— compare failing checks to the baseline list. Non-baseline failure → verdictbroken(the check or the code it pins moved; the fix tranche decides which).python scripts/wheel_smoke.pythenpython -u scripts/wheel_operational_smoke.py— any non-zero exit → verdictbroken, target = the pin named in the output.- RETIRED (operator ruling 2026-08-22, CLAUDE.md §Build and test):
the root sweep is no longer an audit instrument. Do NOT run
tools/root_sweep.py. Writeproof/broken-sweep.txtcontaining the single lineretired 2026-08-22 — see CLAUDE.mdso the proof count stays auditable. - Write
broken.md: the table of every non-baseline delta, one row per finding, columns as the LEDGER. Matches baseline exactly → the table plus one line:all instruments at baseline, with the five proof files as the required proof of looking (G2).
GATE
Pass: every instrument ran (four live instruments + the retirement
marker file = five proof files) AND every non-baseline delta has a
LEDGER row with disposition parked.
Verdict labels: broken | flaky | baseline.
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 · 62 lines · 44 tokens per session scan A fe3db61580cb
dr-audit-broken is a skill published in the GitHub repository AHepi/DeepReason (141 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 715 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.
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…