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 biggora/claude-plugins-registry --skill verify-before-donegit clone --depth 1 https://github.com/biggora/claude-plugins-registryWrote 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/biggora/claude-plugins-registry/verify-before-done)<a href="https://agentmods.dev/skills/biggora/claude-plugins-registry/verify-before-done"><img src="https://agentmods.dev/badge/skills/biggora/claude-plugins-registry/verify-before-done.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.00074 | $0.01102 |
| Opus 5 | $0.00037 | $0.00551 |
| Sonnet 5 | $0.00015 | $0.00220 |
| Haiku 4.5 | $0.00007 | $0.00110 |
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 8d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Before Done
Replace confidence and prior reports with fresh, reproducible evidence. Verify the product behavior, the implementation, and applicable operational readiness before making a completion claim.
Establish the Claims
- Read repository instructions, the accepted specification, acceptance criteria, task-owned diff, and project-defined verification commands.
- List every claim the result must support. Map each claim to an acceptance criterion or state explicitly that the criterion is missing.
- Identify the exact proof for each claim before running anything. Prefer the narrowest project-native check that proves the claim, then add the broader gates required by the changed surface.
- Preserve unrelated and user-owned work. Never use
git reset --hard, destructive cleanup, or a clean-build procedure that deletes unowned files.
Build the Readiness Matrix
Read the readiness matrix before verifying. Create rows across all three levels:
- User readiness: execute the real journey and observable behavior, including relevant failure behavior.
- Engineering readiness: run focused and broader tests plus project-owned type, lint, build, integrity, and security gates applicable to the change.
- Operational readiness: exercise project-defined clean build, start, deploy validation, rollback, and observability checks where applicable and authorized.
Mark a gate required only when the specification, repository, changed surface, or release process makes it required. Mark a genuinely irrelevant gate SKIP with a reason; never use SKIP to avoid an available required check.
Route Product Proof
- Use
test-web-uifor functional web journeys. - Use
test-mobile-appfor mobile application journeys. - Use
ui-auditfor visual quality, accessibility presentation, and localization checks. - Exercise CLI and API behavior through real black-box invocations against their public interface. Do not substitute unit tests for a required user journey.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 70 lines · 74 tokens per session scan A 5225f237b4e1
verify-before-done is a skill published in the GitHub repository biggora/claude-plugins-registry (2 stars, last pushed 10d ago), licensed MIT. It adds 74 tokens to every session and 1,102 once invoked, about $0.0004 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
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
model-merging
Merge multiple fine-tuned models using mergekit to combine capabilities without retraining. Use when creating specialized models by blending domain-specific expertise (math + coding + chat), improving performance beyond single models, or experimenting rapidly with model variants. Covers SLERP, TIES-Merging, DARE, Task…
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
dev-workflow
The complete development workflow for SkillHub contributors including local dev, staging validation, testing, and PR creation. Ensures agents follow the correct sequence of steps.