Borrowing it
Nothing to install: this file belongs to opslane/verify. 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/opslane/verify/main/CLAUDE.mdgit clone --depth 1 https://github.com/opslane/verifyWrote 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/instructions/opslane/verify/claude-md)<a href="https://agentmods.dev/instructions/opslane/verify/claude-md"><img src="https://agentmods.dev/badge/instructions/opslane/verify/claude-md/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/instructions/opslane/verify/claude-md"><img src="https://agentmods.dev/badge/instructions/opslane/verify/claude-md.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.00454 | $0.00454 |
| Opus 5.5 | $0.00182 | $0.00182 |
| Sonnet 5.5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00045 | $0.00045 |
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 29d 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.
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.
skills/verify-setup/SKILL.md one-time repo setup: the setup contract and the app profile.
skills/break/SKILL.md tries to break a change on a disposable local stack.
pipeline/ the engine. A few CLI verbs over 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:
criteriarenders the approval artifact from JSONreportrenders the report from JSONchanged-fileslists behaviour-bearing changed files, and coverage gaps given claimsprofile-checkvalidates.verify/profile.json, the app profile /verify-setup writes
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 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.
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.
- 29d ago Changed · +3 lines · +61 tokens per session 9536102b375b
- 1mo ago First seen · 43 lines · 393 tokens per session scan A 10f6f0e82a87
verify CLAUDE.md is an instructions file published in the GitHub repository opslane/verify (115 stars, last pushed 12d ago), licensed MIT. It adds 454 tokens to every session, about $0.0018 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-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.