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-validate-changenpx skills add AHepi/DeepReason --skill dr-validate-changegit 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-validate-change)<a href="https://agentmods.dev/skills/ahepi/deepreason/dr-validate-change"><img src="https://agentmods.dev/badge/skills/ahepi/deepreason/dr-validate-change.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.00046 | $0.01432 |
| Opus 5 | $0.00023 | $0.00716 |
| Sonnet 5 | $0.00009 | $0.00286 |
| Haiku 4.5 | $0.00005 | $0.00143 |
Grade A, and why
dr-validate-change 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 4d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate the change
Input: SPEC.md's acceptance checks + the finished checklist. Output: VALIDATION.md with verdict PASS or FAIL. You run checks and record outcomes. You do not fix anything — a failure routes back to re-planning with evidence, which is cheaper than a hidden patch that invalidates the checklist's audit trail.
Procedure
-
Re-read REQUEST.md, SPEC.md, CHECKLIST.md in full. Yes, again — this is the phase that catches forgotten requirements, and it can only catch what it re-reads.
-
Run EVERY acceptance check in SPEC.md, in item order, even ones a checklist step already ran — steps prove local progress; this phase proves the assembled whole. Paste each real output.
-
Run the regression ring: the full gate (
pytest tests/ -q -n 4) must end 0 failed. A failure you caused is a FAIL verdict; a pre-existing failure you can prove pre-dates the change (git stash→ rerun →git stash pop) is recorded as such and does not block, but goes to PARKED.md. -
Behavior-preservation spot-check: if the change touched a reader or validator of the append-only record, re-run
verify_rooton one known-good committed root and one defect-era root — prior verdicts must be unchanged except where SPEC.md says otherwise. -
Frozen-surface diff — paste it, empty or explained:
git diff --stat <tranche-base>..HEAD -- \ src/deepreason/capabilities/state.py src/deepreason/harness.py \ src/deepreason/invariants.py src/deepreason/run_manifest.py \ src/deepreason/qualification.pyEmpty output is the expected result and is pasted as proof. Non-empty output is a FAIL unless REQUEST.md quotes the operator approving that exact surface — convention guards these files at design time, but this paste is the one MECHANICAL tripwire on the path, so it is not optional.
-
Packaging-surface check. If the change touched pyproject.toml, CLI entry points, the MCP server surface, or the wheel layout: run
python scripts/wheel_smoke.py(pluspython -u scripts/wheel_operational_smoke.pywhen the operational provider-facing surface moved) and paste the last lines. The smokes pin expected sets and hashes; a surface change whose commit did not update those pins is a FAIL. If the surface did not move, write "packaging surface untouched — smoke not owed": the skip must be a recorded decision, not an omission.
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.
- 4d ago First seen · 118 lines · 46 tokens per session scan A f8fb987cdf52
dr-validate-change is a skill published in the GitHub repository AHepi/DeepReason (140 stars, last pushed 4d ago), licensed MIT. It adds 46 tokens to every session and 1,432 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…