Borrowing it
Nothing to install: this file belongs to AHepi/DeepReason. 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/AHepi/DeepReason/main/.claude/skills/dr-verify-outcome/SKILL.mdgit 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-verify-outcome)<a href="https://agentmods.dev/skills/ahepi/deepreason/dr-verify-outcome"><img src="https://agentmods.dev/badge/skills/ahepi/deepreason/dr-verify-outcome.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.1 | $0.00044 | $0.00881 |
| Opus 5 | $0.00022 | $0.00441 |
| Sonnet 5 | $0.00009 | $0.00176 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
dr-verify-outcome 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 6d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify the outcome
Input: GOAL.md's machine-decidable success criterion + the pushed fix. Output: VERIFY.md with verdict PASS or FAIL. You verify; you do not patch. Any new code change belongs to a fresh cycle through the orchestrator.
Ladder of proof (ascend only as far as the goal requires)
- Criterion command. Run GOAL.md's success command verbatim. Paste output.
- Historical roots. If the fix changed a reader/validator, re-run
verify_rootagainst the committed roots that showed the defect AND one known-good root: the target violations must disappear, everything else must be unchanged. List remaining violations by class — do not summarize them away. - Live run (only if GOAL.md demands live proof). At most ONE
attempt, fully guarded:
- Preflight: env file present,
deepreasonimportable, run identity free (retire + commit rename first if occupied). - Launch detached from the ladder's own directory:
setsid nohup ./<ladder>.sh & disown. - Arm rollback insurance: the snapshot loop (commit+push the
experiment dir every ~5 min) and a monitor on
progress.jsonlstate/phase + the driver log'src=lines, alerting on both success AND failure signatures. - Judge only typed outcomes: run state, stop_reason, audit JSON,
verify_root, FINDINGS.md. Model prose is not verification.
- Preflight: env file present,
- Know what a live run can and cannot prove. Model behavior is stochastic across identically-configured runs (a capability channel used in one attempt may go unused in the next). A live attempt that never reaches the fixed path is INCONCLUSIVE for that path — say so; the offline regression remains the proof of correctness. Do not burn repeated live attempts chasing a stochastic path: one relaunch maximum, then record the residue.
VERIFY.md template
# Verification
Criterion command + output: <pasted>
Historical roots re-checked: <root -> before/after violation classes>
Live attempt (if any): <run id, typed stop, tokens, one-line audit>
Verdict: PASS | FAIL | PASS-offline/INCONCLUSIVE-live
Residue (honest): <what remains unproven or parked, or "none">
Errata: <docs/ERRATA.md entry id(s) added, or "errata: none">
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.
- 6d ago First seen · 74 lines · 44 tokens per session scan A 96c320c4b54c
dr-verify-outcome is a skill published in the GitHub repository AHepi/DeepReason (142 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 881 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…
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…