What is verify CLAUDE.md?

Project instructions for Opslane Verify, a Claude Code plugin that checks whether a software change meets agreed acceptance criteria. Acceptance criteria are specific conditions used to decide whether a change works.

Use them when changing the verification workflow or engine, defining checks, reviewing changed files, finding coverage gaps, or understanding generated verification reports.

They keep checking separate from fixing, so the verification result is based on observed behaviour rather than assumptions from the code diff. They also explain where run reports and the shared skill are stored.

verify CLAUDE.md — Instructions file by opslane

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 instructions/opslane/verify/claude-md

Clone the repo

git clone --depth 1 https://github.com/opslane/verify

Per session 393 This file is loaded in full into every session.

When invoked 393 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00393	$0.00393
Opus 5	$0.00197	$0.00197
Sonnet 5	$0.00079	$0.00079
Haiku 4.5	$0.00039	$0.00039

Measured 3d ago against content hash 10f6f0e82a87, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

verify CLAUDE.md 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 3d 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.

CLAUDE.md · 43 lines

What it actually says

Project

opslane-verify — a Claude Code plugin that verifies a change works. It turns the change's plan into acceptance criteria, stops for approval, then drives the real system and reports what it observed.

Architecture

skills/verify/SKILL.md   the workflow. Claude is the control loop.
pipeline/                the engine. Three CLI verbs over three pure modules.

The skill decides what to check and judges the result. The engine only does plumbing that would be silly to do in markdown:

criteria renders the approval artifact from JSON
report renders the report from JSON
changed-files lists behaviour-bearing changed files, and coverage gaps given claims

Run artifacts land in the target repository under .verify/runs/<id>/ and are gitignored there. The engine holds no state.

Boundaries

The skill never fixes what it judges. It never derives acceptance criteria from the diff alone. It never reads source to decide pass or fail — a criterion that cannot be checked without reading code is the wrong criterion.

Skill sync

skills/ is the source of truth. A PostToolUse hook (.claude/hooks/sync-skill.sh) copies the skill to ~/.claude/skills/ after every Write or Edit. Never edit the copy under ~/.claude/ directly.

Note: an installed plugin resolves the engine through CLAUDE_PLUGIN_ROOT. Set VERIFY_PIPELINE only when running from a development checkout.

Engine work

cd pipeline && npm ci
npm test          # vitest
npm run typecheck # tsc --noEmit, expected clean

The three lib modules are pure functions over plain data. Keep them that way: everything that touches the filesystem, git, or the network lives in cli.ts.

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.

3d ago First seen · 43 lines · 393 tokens per session scan A 10f6f0e82a87

Subscribe to this mod's changes

verify CLAUDE.md is an instructions file published in the GitHub repository opslane/verify (115 stars, last pushed 27d ago), licensed MIT. It adds 393 tokens to every session, about $0.0020 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.

claude claude-code claude-code-plugins claude-code-skill

context-mode CLAUDE.md

Claude Code instructions for mksglu/context-mode, covering context-mode — mandatory routing rules, think in code — mandatory, blocked — do not attempt, curl / wget — blocked and inline http — blocked.

mksglu/context-mode · 1,184 tokens

claude-skills CLAUDE.md

Instructions for secondsky/claude-skills, covering claude skills - project context, ⚠️ critical: communication rule — the most important rule, ⚠️ critical: repository policy - never touch jezweb repo, ❌ forbidden actions (jezweb repo) and ✅ required actions (secondsky repo).

secondsky/claude-skills · 7,874 tokens

verify CLAUDE.md