verification-loop

verification-loop is a skill for Claude Code, Codex from frankxai/claude-skills-library. It costs 49 tokens per session (751 once invoked), scanned A, original, MIT.

A six-step verification routine for changes made on Windows that records either PASS or FAIL before a draft pull request. A pull request is a request for others to review and merge code.

In plain words
What is it for?
Use it after a feature or refactor and before committing, pushing, or passing the work to another agent setup.
Why use it?
It creates a written check before work is committed, uploaded, or handed to another coding system.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it after a feature or refactor and before committing, pushing, or passing the work to another agent setup.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/frankxai/claude-skills-library/verification-loop
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.

Any agent
npx skills add frankxai/claude-skills-library --skill verification-loop
Clone the repo
git clone --depth 1 https://github.com/frankxai/claude-skills-library

Made for: Claude Code, Codex.

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-loop

README.md
[![agentmods](https://agentmods.dev/badge/skills/frankxai/claude-skills-library/verification-loop/github.svg)](https://agentmods.dev/skills/frankxai/claude-skills-library/verification-loop)
Your own site
<a href="https://agentmods.dev/skills/frankxai/claude-skills-library/verification-loop"><img src="https://agentmods.dev/badge/skills/frankxai/claude-skills-library/verification-loop/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.

agentmods 80×15 button for verification-loop

Your own site · 80×15
<a href="https://agentmods.dev/skills/frankxai/claude-skills-library/verification-loop"><img src="https://agentmods.dev/badge/skills/frankxai/claude-skills-library/verification-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 751 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.00049 $0.00751
Opus 5.5 $0.00020 $0.00300
Sonnet 5.5 $0.00010 $0.00150
Haiku 4.5 $0.00005 $0.00075

Measured 4d ago against content hash 4e7b85f2b571, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

verification-loop 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 4d 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.

absorbed/harness/verification-loop/SKILL.md · 52 lines

How it starts

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

Estate verification loop

Run the checks in this order. Stop at the first hard failure. Record a result for every check you could not run. A missing tool is not a pass.

  1. Install and build with the repo's package manager. Prefer pnpm when pnpm-lock.yaml is present. Prefer uv for Python. Do not switch the repo to npm because a snippet says npm run build.
  2. Types. For TypeScript, pnpm exec tsc --noEmit from the package that owns the change. For Python, uv run pyright only when that project already uses it.
  3. Lint with the formatter the repo already configured. Do not add a new linter config to make this step green.
  4. Tests the change can affect. State the command, the pass count, and the fail count from the tool output.
  5. Secret scan of the diff for private-key blocks, sk-ant, GitHub token prefixes, and Slack token prefixes. Reading a local env file during development is normal on this machine. Committing one is not.
  6. git diff --stat against the branch you will push. Name the files. Confirm you did not sweep another agent's untracked work.

How to score

  • Build, types, and tests are hard gates when those tools exist for the files you changed.
  • A coverage number near 80 percent is a target for product code. It does not block a docs-only change or an ops handover.
  • console.log left in application code is a warning. It does not fail the build by itself.
  • If a check cannot run, write NOT RUN and the reason. Do not invent a pass.

Report

VERIFICATION
build:    PASS | FAIL | NOT RUN
types:    PASS | FAIL | NOT RUN
lint:     PASS | FAIL | NOT RUN
tests:    PASS | FAIL | NOT RUN
secrets:  PASS | FAIL | NOT RUN
diff:     <n files>
untracked: <n files>
ready:    YES | NO

Any untracked file makes ready NO. The runner also scans the text of those files. They belong to another session until someone names them in the change.

The person who writes this report does not sign the pull request. Open a draft. A different harness reviews the exact SHA.

Read the full file on GitHub · 52 lines

Files

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.

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. 4d ago Changed · +7 lines 4e7b85f2b571
  2. 5d ago First seen · 45 lines · 49 tokens per session scan A 4b8ddfce989d

Subscribe to this mod's changes

verification-loop is a skill published in the GitHub repository frankxai/claude-skills-library (47 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 751 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-10-11.