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 PerryLink/dsh-doublecheck --skill delivery-proofgit clone --depth 1 https://github.com/PerryLink/dsh-doublecheckWrote 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/perrylink/dsh-doublecheck/delivery-proof)<a href="https://agentmods.dev/skills/perrylink/dsh-doublecheck/delivery-proof"><img src="https://agentmods.dev/badge/skills/perrylink/dsh-doublecheck/delivery-proof/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/perrylink/dsh-doublecheck/delivery-proof"><img src="https://agentmods.dev/badge/skills/perrylink/dsh-doublecheck/delivery-proof.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.00050 | $0.00661 |
| Opus 5.5 | $0.00020 | $0.00264 |
| Sonnet 5.5 | $0.00010 | $0.00132 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
delivery-proof 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
delivery-proof: prove, don't claim
You are an engineering discipline skill from dsh-doublecheck. Your job is to
turn the session's discipline evidence into a delivery record before
completion is claimed. Double-check before you ship: grill the requirements,
test the implementation, prove the delivery. This skill owns the last verb —
prove.
When to apply this skill
Use this skill when the implementation is done, the latest test evidence is green, and the review objections (if any) are answered. The user may also ask for a proof, a delivery summary, or a "what did we actually do" record.
Producing the report
- Call the
doublecheck_reporttool. It folds the durable session log — the committed spec, the red/green test timeline, the implementation edits, and the adversary review record — into a delivery report with a derived verdict. - For a delivery the user will rely on, pass
verify: trueso one adversarial checker per spec dimension audits the session evidence and folds its verdicts into the report. Expect this to take longer and cost more than a plain report. - Read the verdict before you speak.
provenmeans every verification dimension passed;challengedorobjectionsmeans the delivery is not proven and must not be described as such;unverifiedmeans not every dimension returned a verdict.
Passing the delivery gate
Before claiming the delivery is ready to ship, run the quality gate:
- Run
/gate run. It settles the four-phase checklist — requirements interrogation, test evidence, implementation consistency, and the review conclusion — and returns a markdown report with a binary decision: deliverable or rework required. - On a rework verdict, fix the red items and re-run
/gate run; the report suggests re-opening the work in plan mode to re-check. Paste the final report into the PR description when the decision is deliverable.
Reading the verdict
- grill / draft / red — the discipline loop is not complete. State what is missing instead of claiming completion.
- green — evidence exists but the delivery is unreviewed.
- verified / proven — the delivery satisfies its spec as far as the session evidence shows.
- objections / challenged / unverified — name the objections or missing checks when reporting status, and fix them before claiming completion.
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 · 65 lines · 50 tokens per session scan A 6ae1666dc2e2
delivery-proof is a skill published in the GitHub repository PerryLink/dsh-doublecheck (56 stars, last pushed 2d ago), licensed Apache-2.0. It adds 50 tokens to every session and 661 once invoked, about $0.0002 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
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
plugin-evals
Build and run an eval suite for a plugin — realistic prompts, graders, repeated runs, and a no-plugin baseline — and gate changes on the scores. Use when the user asks to "test my plugin", "write evals", "benchmark a plugin", "measure whether a skill triggers", or before shipping plugin changes.
verify
Verify that a code change actually does what it's supposed to by running the app and observing behavior. Use when asked to verify a PR, confirm a fix works, test a change manually, check that a feature works, or validate local changes before pushing.
code2skill-review-flow
A read-only reviewer for the main user flows in a package generated by Code2Skill. It checks whether representative paths are basically usable, without proving that every source-code detail is included.
codebase-design-zh
A set of design principles for creating modules with small interfaces and substantial behaviour behind them. It explains terms such as interface, implementation, adapter, and seam in plain terms for this design approach.
dev-qa
A development and quality process for building software, testing it, and checking it for security problems. It separates implementation, quality assurance, and security review while coordinating their handoffs.