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 bostonaholic/rpikit --skill verification-before-completiongit clone --depth 1 https://github.com/bostonaholic/rpikitWrote 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/bostonaholic/rpikit/verification-before-completion)<a href="https://agentmods.dev/skills/bostonaholic/rpikit/verification-before-completion"><img src="https://agentmods.dev/badge/skills/bostonaholic/rpikit/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/bostonaholic/rpikit/verification-before-completion"><img src="https://agentmods.dev/badge/skills/bostonaholic/rpikit/verification-before-completion.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 280 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
- medium Excessive Agency · line 15 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 170 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 270 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00038 | $0.01438 |
| Opus 5 | $0.00019 | $0.00719 |
| Sonnet 5 | $0.00008 | $0.00288 |
| Haiku 4.5 | $0.00004 | $0.00144 |
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 10d 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Before Completion
Evidence before claims, always. No completion claims without fresh verification.
Purpose
Claiming work is done without verification breaks trust and wastes time. This skill enforces running verification commands and confirming output before any success claim. "It should work" is not verification.
The Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE.
Every claim must be backed by evidence you just observed. Not evidence from earlier. Not evidence you expect. Evidence you just saw.
The Five-Step Gate
Before any completion claim, complete these steps:
Step 1: Identify
What command proves your claim?
Claim: "Tests pass"
Command: npm test (or project's test command)
Claim: "Build succeeds"
Command: npm run build (or project's build command)
Claim: "Lint is clean"
Command: npm run lint (or project's lint command)
Claim: "Bug is fixed"
Command: The reproduction steps that previously failed
Step 2: Run
Execute the command freshly. Not from cache. Not from memory.
Run the command NOW.
Wait for it to complete.
Do not proceed until finished.
Step 3: Read
Read the COMPLETE output.
- Exit code (0 = success)
- All output lines, not just the last one
- Any warnings (not just errors)
- Summary statistics if provided
Step 4: Verify
Confirm the output supports your claim.
Claim: "Tests pass"
Verify: Exit code 0, "X tests passed", no failures
Claim: "Build succeeds"
Verify: Exit code 0, output files created, no errors
Claim: "Bug is fixed"
Verify: Previous failure no longer occurs
Step 5: Claim
Only NOW make your completion claim.
"Tests pass" - after seeing test output showing success
"Build succeeds" - after seeing build complete without errors
"Implementation complete" - after all verifications pass
Common Failure Modes
Tests
What to run: Project test command
What to verify:
- Exit code 0
- All tests pass (not just "some tests ran")
- No skipped tests (unless intentional)
- No test warnings
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.
- 10d ago First seen · 282 lines · 38 tokens per session scan A 467e9d7986ea
verification-before-completion is a skill published in the GitHub repository bostonaholic/rpikit (20 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 1,438 once invoked, about $0.0002 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-30.
Other skills, from other repositories
implement-universal
Harness-agnostic version of /implement. Drives a single workshop ticket through the SWE→Tester loop in ONE conversation, with the role prompts bundled as agents/software-engineer.md and agents/tester.md instead of being launched as subagents. Resolves the ticket from implementyourself/tasks/, creates an…
credit-note-fixer
Fix the tiny credit-note formatting bug and rerun the exact targeted test command.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
trulens-running-evaluations
Execute TruLens evaluations and view results.
test-writer
How to write pytest tests for modules in this workspace. Load whenever you are about to write or extend tests.
review
Enter the Review phase of CocoBrew. Aggregates findings from Code Quality Advisor, CocoCupper intelligence, spec compliance check, and decision coverage gate. Produces review.md with decision points. Requires developer approval before $ship can proceed.