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 duthaho/claudekit --skill verification-gategit clone --depth 1 https://github.com/duthaho/claudekitWrote 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/duthaho/claudekit/verification-gate)<a href="https://agentmods.dev/skills/duthaho/claudekit/verification-gate"><img src="https://agentmods.dev/badge/skills/duthaho/claudekit/verification-gate.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.00087 | $0.02622 |
| Opus 5 | $0.00044 | $0.01311 |
| Sonnet 5 | $0.00017 | $0.00524 |
| Haiku 4.5 | $0.00009 | $0.00262 |
Grade A, and why
verification-gate scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. If a service endpoint: hit it with `curl` or your project's HTTP test tool. How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Gate
Overview
A pre-completion gate that converts the assertion "this is done" into evidence: the test output, the command run, the behavioral observation. The skill exists because "done" is a self-reported state and self-reports are wrong roughly half the time on real changes. The gate is short — five minutes — but it catches the class of mistake where an engineer claims a fix works after only running tests in their IDE, only verifying happy-path, only checking a single environment. This is the load-bearing skill of v4: every other skill funnels through it before its work is called done.
When to Use
- Before opening a PR for review
- Before declaring a bug fixed in response to a ticket or incident
- Before checking off an
Acceptance:line in a plan - Before pushing to a branch that triggers a deploy
- Whenever you catch yourself thinking "I'm done" — pause and run this gate
When NOT to Use
- During exploratory work where "done" doesn't apply yet
- Mid-implementation, when the partial work is committed for checkpoint reasons but not claimed complete
- For changes already merged and ack'd — the gate is pre-completion, not post-completion
Process
Step 1: Restate the claim
Goal: Make the "done" claim explicit and falsifiable.
Inputs: Whatever you were about to call done.
Actions:
- Write one sentence:
I am claiming <X> is complete because <Y>.X is the work; Y is the evidence you intend to show. Don't do anything else until you've written it. - If Y is "tests pass and the code looks right," return to Step 2 — the evidence is too vague.
Output: A claim sentence written down (PR description, scratch file, or comment).
Step 2: Run the named tests with full output
Goal: Prove the tests asserting this work pass, with evidence pasted.
Inputs: The list of tests relevant to this work.
Actions:
- Run the project's test command for this scope. Use the exact form from the
plan's
Acceptance:line if it exists. - Capture the full output, not just "PASSED." The output should show test names and a pass count.
- Run the broader suite for the file or module — confirm no regressions.
- Paste the output (or a referenced artifact) into the PR / scratch file.
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.
- 7d ago First seen · 198 lines · 87 tokens per session scan A 3fb18a0c409e
verification-gate is a skill published in the GitHub repository duthaho/claudekit (97 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 2,622 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
grant-proposal-builder
Nonprofit and research grant proposal assembly with structured sections, budget templates, and evaluation alignment. Use when writing grant proposals, funding applications, or research funding requests.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
audio-production
Professional audio production for music, podcasts, and sound design. Use when working with audio recording, mixing, mastering, or sound design for any medium.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.