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 agentmods add skills/kbwen/agentic-os/verification-before-completionnpx skills add KbWen/agentic-os --skill verification-before-completiongit clone --depth 1 https://github.com/KbWen/agentic-osWrote 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/kbwen/agentic-os/verification-before-completion)<a href="https://agentmods.dev/skills/kbwen/agentic-os/verification-before-completion"><img src="https://agentmods.dev/badge/skills/kbwen/agentic-os/verification-before-completion.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 | $0.00022 | $0.00329 |
| Opus 5 | $0.00011 | $0.00164 |
| Sonnet 5 | $0.00004 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- verification-before-completion — 100% identical, 0 lines differ
What it actually says
Verification Before Completion
Overview
Any "completed" statement MUST be supported by evidence. This skill provides a pre-completion Gate Function, ensuring results are reproducible, traceable, and deliverable.
Ironclad Rules
- No evidence = no completion claim.
- Evidence MUST be reproducible by others; verbal descriptions are NOT accepted.
- If tests/checks fail, the status MUST revert to in-progress.
When to Use
- Tasks are preparing to enter
/ship. - Before submitting PRs or handing off work.
- After completing high-risk changes (data, permissions, core flows).
Gate Function
- Scope Gate: Confirm changes only cover the agreed scope.
- Quality Gate: Execute required tests and static checks.
- Evidence Gate: Compile reproducible evidence (commands, outputs, versions).
- Risk Gate: Confirm rollback strategies and known risks.
- Communication Gate: Output a completion summary (changes, validation, constraints).
Minimum Evidence Checklist
- At least one set of tests/checks directly related to this change.
- Specific execution commands and results (Success/Failure/Warning).
- If there are unfinished items, explicitly mark them with follow-up suggestions.
Common Mistakes
- Claiming "it should work" without any output evidence.
- Testing only the happy path, missing regressions or edge cases.
- Treating old test results as evidence for new changes.
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.
- 5d ago First seen · 43 lines · 22 tokens per session scan A de3689a78eda
verification-before-completion is a skill published in the GitHub repository KbWen/agentic-os (157 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 329 once invoked, about $0.0001 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
orloj-generator
Interactive scaffold generator for Orloj multi-agent systems. Use this skill whenever someone wants to create, set up, scaffold, bootstrap, or generate an Orloj agent system, pipeline, swarm, or hierarchy. Also trigger when users mention "orlojctl init", ask how to get started with Orloj, want to build a multi-agent…
season-words
Use when a haiku needs a seasonal reference (kigo). Lists season words to weave in.
muster-frappe-release
Build, seed, deploy, break, measure, and prove a Muster Frappe release. Use for bench or site setup, migrations, realistic ERPNext data, role matrices, browser/mobile QA, performance and recovery tests, release evidence, Frappeverse demos, or normal-speed presentation video.
muster-frappe-security
Threat-model and negatively verify Muster integrations with Frappe OAuth, multi-tenancy, RBAC, field permissions, agent delegation, channels, secrets, approvals, and audit logs. Use for identity linking, site registration, Telegram onboarding, policy changes, permission tests, or security release gates.
muster-frappe-workflows
Design and implement durable multi-step Muster workflows for Frappe with agent, subagent, and nested task graphs. Use for workflow definitions, planning, delegation, tool policies, approvals, retries, schedules, triggers, artifacts, dynamic page creation, or Claude-style universal JS and JSON automation.
muster-frappe-metadata
Design, generate, review, apply, and roll back Frappe or ERPNext metadata changes through Muster. Use for DocTypes, child tables, custom fields, property setters, workflows, roles, permissions, reports, print formats, web pages, workspaces, fixtures, patches, or installed-app compatibility.