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 Pixel-Process-UG/superkit-agents --skill verification-before-completiongit clone --depth 1 https://github.com/Pixel-Process-UG/superkit-agentsWrote 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/pixel-process-ug/superkit-agents/verification-before-completion)<a href="https://agentmods.dev/skills/pixel-process-ug/superkit-agents/verification-before-completion"><img src="https://agentmods.dev/badge/skills/pixel-process-ug/superkit-agents/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/pixel-process-ug/superkit-agents/verification-before-completion"><img src="https://agentmods.dev/badge/skills/pixel-process-ug/superkit-agents/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.00042 | $0.02513 |
| Opus 5.5 | $0.00017 | $0.01005 |
| Sonnet 5.5 | $0.00008 | $0.00503 |
| Haiku 4.5 | $0.00004 | $0.00251 |
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.
How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
The verification-before-completion skill is the terminal checkpoint for every task in the toolkit. It enforces a strict 5-step protocol that requires running fresh verification commands, reading their full output, and confirming results match the completion claim. Without this skill, agents make unverified claims that lead to broken code in production — with it, every completion claim is backed by evidence.
Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE.
You cannot say "it works," "it's done," "the bug is fixed," or "the feature is complete" without running verification commands and reading their output in this session. Cached results, previous runs, and assumptions do not count.
Phase 1: Identify Verification Commands
Before running anything, explicitly list what needs to pass for this specific task:
| Verification Type | Example Commands | When Required |
|---|---|---|
| Unit tests | npm test, pytest, go test ./..., cargo test, php artisan test |
Always |
| Integration tests | npm run test:integration, pytest tests/integration/ |
When applicable |
| Type checking | tsc --noEmit, mypy ., pyright, phpstan analyse |
When project uses type checking |
| Linting | eslint ., ruff check ., golint ./..., php-cs-fixer fix --dry-run |
Always |
| Build | npm run build, cargo build, go build ./... |
Always |
| Format check | prettier --check ., black --check ., gofmt -l ., pint --test |
When project uses formatters |
Action: List which of these apply to the current project. Not all projects have all types. Be explicit about what you will run and why.
STOP: Do NOT proceed to running commands until you have identified ALL applicable verification types.
Phase 2: Run Commands Fresh
Execute every verification command identified in Phase 1.
| Rule | Rationale |
|---|---|
| Run AFTER the latest code change | Pre-change results are stale |
| Run the FULL suite, not a subset | Subset runs miss regressions |
| Do NOT rely on cached results | Code changed since last run |
| Do NOT skip commands because "they passed earlier" | Earlier is not now |
| If a command takes >5 minutes, note it | Explain what was run instead |
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 · 233 lines · 42 tokens per session scan A 1e0e638f5916
verification-before-completion is a skill published in the GitHub repository Pixel-Process-UG/superkit-agents (3 stars, last pushed 7mo ago), licensed MIT. It adds 42 tokens to every session and 2,513 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-09-03.
Other skills, from other repositories
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. Use when asked to add tests to a function, fix a bug…
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…
verification-before-completion
A checklist for verifying work before claiming that it is finished, fixed, built, tested, or ready to submit. It requires fresh command output and evidence for each claim.
writing-skills
A guide for creating and testing reusable instructions for AI agents, called skills. It applies test-driven development, or TDD—the practice of writing tests before implementation—to instruction documents.
test-driven-development
Test-driven development, or TDD, is a way to build software by writing a test that fails, adding the smallest code that makes it pass, and then cleaning up the code. These instructions require that process for features, bug fixes, refactors, and behavior changes.
test-slack-app
Use when a developer wants to test, try out, smoke-test, verify, or confirm that a Slack app built with the Slack CLI (or a plain Bolt app) actually works, by running it in a developer sandbox or a Free Team, never a workspace with real users, with slack run and exercising its real slash commands, shortcuts, events…