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 skywalkercyt/mp-implement --skill verification-before-completiongit clone --depth 1 https://github.com/skywalkercyt/mp-implementWrote 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/skywalkercyt/mp-implement/verification-before-completion)<a href="https://agentmods.dev/skills/skywalkercyt/mp-implement/verification-before-completion"><img src="https://agentmods.dev/badge/skills/skywalkercyt/mp-implement/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/skywalkercyt/mp-implement/verification-before-completion"><img src="https://agentmods.dev/badge/skills/skywalkercyt/mp-implement/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.00383 |
| Opus 5.5 | $0.00017 | $0.00153 |
| Sonnet 5.5 | $0.00008 | $0.00077 |
| Haiku 4.5 | $0.00004 | $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
Adapted skill — discipline originating in Superpowers v5.1.0 (MIT, Jesse Vincent), rewritten in mattpocock-skills style. The honesty gate in
/mp-implement-issuestep 7 and both pipelines' harvest — no slice counts as done until it passes.
Iron law: no completion or success claim without fresh verification evidence produced in this step. A claim made before its verification is a guess dressed as a fact.
The gate
For each claim you are about to make:
- Name the command that proves it.
- Run that command in full — fresh, in this step.
- Read the complete output and the exit code.
- If the output confirms the claim, make the claim and quote the evidence ("34/34 pass", "exit 0"). If it contradicts the claim, state the actual status with the evidence instead.
Evidence means output from the run you just did. "Should pass", an earlier run, a partial check, a linter where tests are owed, or another agent's self-report are not evidence — a sub-agent's "success" is a lead to verify (check the diff), not a result.
Regression tests
A regression test proves red-green: revert the fix and watch the test fail, restore the fix and watch it pass. A test that never failed proves nothing about the fix.
Requirements
"Tests pass" is not "requirements met". Close out by re-reading the source checklist (issue, spec, plan) and verifying each requirement line by line; report any gap as its actual status.
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 · 30 lines · 42 tokens per session scan A e409549c59a8
verification-before-completion is a skill published in the GitHub repository skywalkercyt/mp-implement (2 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 383 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-08-31.
Other skills, from other repositories
game-qa
Verify a game with evidence on its selected target runtime. Launch the actual build and prove real rendering, input, the core loop, at least one designed outcome, restart, and explicit limitations without dressing subjective fun up as a certain verdict. Use for test a generated game, QA a game build, check whether the…
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.