Borrowing it
Nothing to install: this file belongs to OutlitAI/outlit-sdk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/OutlitAI/outlit-sdk/main/.agents/skills/verification-before-completion/SKILL.mdgit clone --depth 1 https://github.com/OutlitAI/outlit-sdkWrote 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/outlitai/outlit-sdk/verification-before-completion)<a href="https://agentmods.dev/skills/outlitai/outlit-sdk/verification-before-completion"><img src="https://agentmods.dev/badge/skills/outlitai/outlit-sdk/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/outlitai/outlit-sdk/verification-before-completion"><img src="https://agentmods.dev/badge/skills/outlitai/outlit-sdk/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.00043 | $0.00913 |
| Opus 5.5 | $0.00017 | $0.00365 |
| Sonnet 5.5 | $0.00009 | $0.00183 |
| Haiku 4.5 | $0.00004 | $0.00091 |
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.
This is a copy
100% identical to verification-before-completion — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Before Completion
Overview
Core principle: Evidence before claims, always.
Violating the letter of this rule is violating the spirit of this rule.
The Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
Evidence must apply to the current files, inputs, and environment. Reuse a passing result from this task while those remain unchanged. Re-run affected checks after relevant changes, failures, or unresolved concerns, not merely because a new message or review round started.
The Gate Function
BEFORE claiming any status or expressing satisfaction:
1. IDENTIFY: What command proves this claim?
2. RUN OR REUSE: Run the appropriate check, or inspect a still-valid result for the same files, inputs, and environment
3. READ: Full output, check exit code, count failures
4. VERIFY: Does output confirm the claim?
- If NO: State actual status with evidence
- If YES: State claim WITH evidence
5. ONLY THEN: Make the claim
Skip any step = lying, not verifying
Common Failures
| Claim | Requires | Not Sufficient |
|---|---|---|
| Tests pass | Applicable test output: 0 failures | Stale or unrelated output, "should pass" |
| Linter clean | Linter output: 0 errors | Partial check, extrapolation |
| Build succeeds | Build command: exit 0 | Linter passing, logs look good |
| Bug fixed | Test original symptom: passes | Code changed, assumed fixed |
| Regression test works | Red-green cycle verified | Test passes once |
| Agent completed | VCS diff shows changes | Agent reports "success" |
| Requirements met | Line-by-line checklist | Tests passing |
Red Flags - STOP
- Using "should", "probably", "seems to"
- Expressing satisfaction before verification ("Great!", "Perfect!", "Done!", etc.)
- About to commit/push/PR without verification
- Trusting agent success reports
- Relying on partial verification
- Thinking "just this once"
- Tired and wanting work over
- ANY wording implying success without having run verification
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 Changed f66521b4a838
- 2mo ago First seen · 121 lines · 43 tokens per session scan A 2befe7fc55bc
verification-before-completion is a skill published in the GitHub repository OutlitAI/outlit-sdk (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 43 tokens to every session and 913 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to verification-before-completion, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…
dcc-blender-assembly-pitfalls
Read this BEFORE writing any Blender geometry code through MCP, whenever you are about to (1) create or size mesh primitives - bpy.ops.mesh.primitivecubeadd, primitivecylinderadd, primitiveuvsphereadd, primitiveconeadd - or set scale / dimensions on a part; (2) orient a part with rotationeuler or rotationquaternion…
client-scripts
Write ServiceNow client scripts (onLoad/onChange/onSubmit/onCellEdit) using gform, guser, GlideAjax, field visibility/mandatory toggles, and validation with debounced server calls.
color-theory
Use when constructing a reusable palette for a visual system: choose a harmony, assign semantic roles and light/dark token values, account for brand and cultural meaning plus color-vision deficiency, and ensure interaction states never rely on hue alone. Not for measuring an existing interface against an accessibility…
linkding
Manage bookmarks with Linkding. Use when the user asks to "save a bookmark", "add link", "search bookmarks", "list my bookmarks", "find saved links", "tag a bookmark", "archive bookmark", "check if URL is saved", "list tags", "create bundle", or mentions Linkding bookmark management.
quantum-algorithms
A routing workflow for choosing an open-source quantum-computing algorithm and loading the matching local workflow. Quantum computing uses circuits and quantum states to represent and process information.