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 Vimalk0703/shipworthy --skill verification-before-completiongit clone --depth 1 https://github.com/Vimalk0703/shipworthyWrote 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/vimalk0703/shipworthy/verification-before-completion)<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/verification-before-completion"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/verification-before-completion/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/vimalk0703/shipworthy/verification-before-completion"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/verification-before-completion.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.00029 | $0.00383 |
| Opus 5.5 | $0.00012 | $0.00153 |
| Sonnet 5.5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
verification-before-completion 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
Verification Before Completion
The Iron Rule
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE.
The 5-Step Gate
Step 1: Identify the Proof Command
What command proves this works?
npm test/pytest/go test ./...npm run build/tsc --noEmitnpm run lint- A specific test file:
npx vitest run src/services/user.test.ts
Step 2: Run It
Execute the command. Do not skip this step.
Step 3: Read the Output
Read the FULL output — not just "it passed." Look for warnings, skipped tests, deprecation notices.
Step 4: Verify Your Claim Matches Reality
Does the output actually prove what you're about to claim? "All 47 tests pass" is verifiable. "It should work correctly" is not.
Step 5: Assert with Evidence
Now claim completion, citing evidence:
- "All 47 tests pass (including 3 new tests for the user service)"
- "Build completes with 0 errors and 0 warnings"
Red Flag Language
If you catch yourself about to say any of these, STOP — you haven't verified:
- "should work"
- "probably fine"
- "I believe this is correct"
- "this looks right"
- "I'm confident that..."
- "based on my understanding..."
Replace with: "Let me verify." Then run the command.
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 · 47 lines · 29 tokens per session scan A 10c6aec9dc1d
verification-before-completion is a skill published in the GitHub repository Vimalk0703/shipworthy (6 stars, last pushed 6mo ago), licensed MIT. It adds 29 tokens to every session and 383 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-09-03.
Other skills, from other repositories
dare-execute
Executa uma task específica com implementação de código e testes. Use quando o usuário aprovar TASKS.md e quiser executar uma task. Implementa o código, roda testes (Ralph Loop) e valida até passar.
dare-bench
Roda o harness determinístico de fixtures de verificação (Fix·Rate, solve-rate, baseline). Mapeia o CLI dare bench.
dare-guard
Run the DARE security guard gate on artifacts (dare guard).
team-qa
Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.
regression-suite
Map test coverage to GDD critical paths, find fixed bugs lacking regression tests, flag drift from new features.
soak-test
Soak test protocol for extended play — what to observe and log for slow leaks, fatigue, late-appearing edge cases.