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 skills add amplifthq/oh-my-dsh --skill verify-before-donegit clone --depth 1 https://github.com/amplifthq/oh-my-dshWrote 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/amplifthq/oh-my-dsh/verify-before-done)<a href="https://agentmods.dev/skills/amplifthq/oh-my-dsh/verify-before-done"><img src="https://agentmods.dev/badge/skills/amplifthq/oh-my-dsh/verify-before-done/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/amplifthq/oh-my-dsh/verify-before-done"><img src="https://agentmods.dev/badge/skills/amplifthq/oh-my-dsh/verify-before-done.svg" alt="Reviewed on agentmods" width="80" 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.00022 | $0.00147 |
| Opus 5.5 | $0.00009 | $0.00059 |
| Sonnet 5.5 | $0.00004 | $0.00029 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
verify-before-done 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.
What it actually says
Verify before done
- Identify the exact command or observation that proves each claim.
- Run it fresh after the final edit.
- Read the complete exit status and relevant output; do not infer one check from another.
- For a bug fix, reproduce the original symptom or run a regression test that exercises it.
- Reconcile the implementation against every requested requirement, not only the passing tests.
- Report the evidence and any check that could not be run. Never replace missing evidence with confidence language.
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 · 15 lines · 22 tokens per session scan A bef279c470b1
verify-before-done is a skill published in the GitHub repository amplifthq/oh-my-dsh (16 stars, last pushed 10d ago), licensed MIT. It adds 22 tokens to every session and 147 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
dsh-tui-guide
Use when the user asks about dsh-tui itself (usage, shortcuts, config, themes, migration, VS Code). Load before answering; skip for normal coding tasks.
modsearch
Plug-in web search, X (Twitter) search, and page fetch for models without native web access. Use whenever the task needs current information, external facts, source links, posts from X, or the content of a specific URL, and the active model/harness has no native search or fetch tool. Runs the modsearch CLI to return…
dsh-plugin-guide
Use when developing, reviewing, packaging, debugging, or answering questions about DeepSeek Harness (DSH) plugins — the plugin-based agent harness on vendored Cordis. Applies the official plugin-development constraints (plugin contract, cordis.yml layers, services/events/effects, tool DSL, bundles/profiles) backed by…
dsh-plugin-dev
A guide for building and debugging plugins for DeepSeek Harness, a developer-preview tool built on the Cordis component framework. It explains how plugins are exported, loaded, and connected to services.
dsh-first-plugin
A step-by-step guide for building and installing a first DSH plugin. DSH is a software tool whose plugins can add tools, connect outside services, or respond to agent events.
dsh-onboarding
Guidance for helping someone use DeepSeek Harness, a local runtime for coding agents, for the first time. It explains the runtime, profiles, workspace, permissions, and how extensions are discovered.