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 redhuntlabs/wizard --skill verifying-before-shippinggit clone --depth 1 https://github.com/redhuntlabs/wizardWrote 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/redhuntlabs/wizard/verifying-before-shipping)<a href="https://agentmods.dev/skills/redhuntlabs/wizard/verifying-before-shipping"><img src="https://agentmods.dev/badge/skills/redhuntlabs/wizard/verifying-before-shipping.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.00027 | $0.00927 |
| Opus 5 | $0.00014 | $0.00464 |
| Sonnet 5 | $0.00005 | $0.00185 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
verifying-before-shipping 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verifying Before Shipping
What this does
Forces a verification pass before any "this is done" declaration. Works for shipped code, sent docs, published posts, completed tasks, and finished plans.
When to use
- About to mark a task done in a tracker
- About to send a "this is shipped" message
- About to close a ticket / PR / case
- About to tell someone "all set"
What you bring (Inputs)
- The work being declared done
- The original definition of done (or an inferred one if none was set)
What you get (Output)
Either: confirmation the work is genuinely done (and a "done" declaration), or a list of the specific gaps that must close first.
How it works (Steps)
This is a discipline. The behavioral structure is: a non-negotiable rule (below), an excuses-and-counters table to defeat rationalizations, warning signs to spot the moment of risk, and a hard gate that fires before any "done" declaration. Apply the gate; verify each acceptance criterion against actual evidence; declare done only on a clean pass.
The non-negotiable rule
Before declaring any work done, run the verification — actually run it, do not assert it from memory.
Excuses and counters
| If you think... | Reality |
|---|---|
| "I just finished it, of course it works" | Just-finished work has the highest bug density. Verify. |
| "I already manually checked everything" | Manual checking is unreliable. Run the verification step. |
| "The user is in a hurry" | The user is more in a hurry to not have a regression. Verify. |
| "It's a tiny change" | Tiny changes break things in small ways that are hard to find later. Verify. |
| "I'll verify and ship in parallel" | "In parallel" usually means "ship now and verify if there's a complaint." Verify first. |
| "Verification is overkill for this" | Then you don't actually know it's done. Verify. |
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 · 93 lines · 27 tokens per session scan A 7abf1db5d05d
verifying-before-shipping is a skill published in the GitHub repository redhuntlabs/wizard (9 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 927 once invoked, about $0.0001 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-31.
Other skills, from other repositories
fastapi
A Python framework for building web APIs, which are interfaces that let programs communicate over HTTP. It supports request validation, automatic API documentation, asynchronous code, reusable dependencies, and common authentication methods.
lazydocker
A keyboard-driven terminal interface for managing Docker, a system for running applications in isolated containers.
fzf
A command-line tool for finding items by typing partial text, with results updating as you type. It can search files, shell command history, processes, directories, Git branches, commits, and other text output.
glances
A guide for using Glances, a cross-platform system-monitoring tool that displays computer resource and process information in a terminal, browser, or API.
paper-checking
A Windows application for finding copied text in documents. It compares files with a reference collection or compares documents in the same batch with one another.
you-get
A command-line tool for downloading videos, audio, and images from websites such as YouTube and Bilibili.