verification-before-completion

verification-before-completion is a skill for Claude Code from dork-labs/dorkos. It costs 43 tokens per session (1,322 once invoked), scanned A, a copy of verification-before-completion, MIT.

A checklist for verifying software work before saying it is complete, fixed, or passing.

In plain words
What is it for?
Use it before commits or pull requests to run the relevant project checks and confirm their output.
Why use it?
It requires fresh evidence from tests, linting, or type checks so completion claims are not based on assumptions.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents).

Part of the flow plugin — 33 skills, 42 commands, 5 agents, 4 hooks, 5 plugins shipped together

Install

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.

agentmods
npx agentmods add skills/dork-labs/dorkos/verification-before-completion
Any agent
npx skills add dork-labs/dorkos --skill verification-before-completion
Clone the repo
git clone --depth 1 https://github.com/dork-labs/dorkos

Made for: Claude Code.

Or install flow, the plugin that ships this one along with the rest of its 33 skills, 42 commands, 5 agents, 4 hooks, 5 plugins.

Wrote 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.

agentmods badge for verification-before-completion

README.md
[![agentmods](https://agentmods.dev/badge/skills/dork-labs/dorkos/verification-before-completion.svg)](https://agentmods.dev/skills/dork-labs/dorkos/verification-before-completion)
Your own site
<a href="https://agentmods.dev/skills/dork-labs/dorkos/verification-before-completion"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/verification-before-completion.svg" alt="Measured on agentmods" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,322 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 83% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.01322
Opus 5 $0.00022 $0.00661
Sonnet 5 $0.00009 $0.00264
Haiku 4.5 $0.00004 $0.00132

Measured 6d ago against content hash 53efbd34a03c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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 6d 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.

Origin

This is a copy

83% identical to verification-before-completion — 116 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.

.agents/skills/verification-before-completion/SKILL.md · 179 lines

How it starts

The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Verification Before Completion

Overview

Claiming work is complete without verification is dishonesty, not efficiency.

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

If you haven't run the verification command in this message, you cannot claim it passes.

The Gate Function

BEFORE claiming any status or expressing satisfaction:

1. IDENTIFY: What command proves this claim?
2. RUN: Execute the FULL command (fresh, complete)
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

DorkOS Verification Commands

Claim Command What to check
Tests pass (full run) pnpm test -- --run 0 failures, exit 0
Single test file pnpm vitest run <path-to-test-file> 0 failures, exit 0
Linter clean pnpm lint 0 errors, 0 warnings
Types check pnpm typecheck 0 errors across all packages
Build succeeds pnpm build exit 0 for all packages

Gotcha: never use bare pnpm vitest run for a full run — in the dev environment it falsely fails 2 tests; full runs must go through Turborepo (pnpm test -- --run).

When scoped to a single package, prefer filtered commands:

  • pnpm vitest run apps/server/src/path/to/test.ts
  • pnpm --filter @dorkos/server typecheck

Common Failures

Claim Requires Not Sufficient
Tests pass Test command output: 0 failures Previous run, "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

Read the full file on GitHub · 179 lines

Changes

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.

  1. 6d ago First seen · 179 lines · 43 tokens per session scan A 53efbd34a03c

Subscribe to this mod's changes

verification-before-completion is a skill published in the GitHub repository dork-labs/dorkos (9 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 1,322 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to verification-before-completion, differing in 116 lines, and is treated as a copy.