Borrowing it
Nothing to install: this file belongs to Infopibe/everything-claude-code. 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/Infopibe/everything-claude-code/main/.opencode/commands/verify.mdgit clone --depth 1 https://github.com/Infopibe/everything-claude-codeWrote 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/commands/infopibe/everything-claude-code/verify)<a href="https://agentmods.dev/commands/infopibe/everything-claude-code/verify"><img src="https://agentmods.dev/badge/commands/infopibe/everything-claude-code/verify/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/commands/infopibe/everything-claude-code/verify"><img src="https://agentmods.dev/badge/commands/infopibe/everything-claude-code/verify.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.00006 | $0.00398 |
| Opus 5.5 | $0.00002 | $0.00159 |
| Sonnet 5.5 | $0.00001 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
verify 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 verify — 0 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.
What it actually says
Verify Command
Run verification loop to validate the implementation: $ARGUMENTS
Your Task
Execute comprehensive verification:
- Type Check:
npx tsc --noEmit - Lint:
npm run lint - Unit Tests:
npm test - Integration Tests:
npm run test:integration(if available) - Build:
npm run build - Coverage Check: Verify 80%+ coverage
Verification Checklist
Code Quality
- No TypeScript errors
- No lint warnings
- No console.log statements
- Functions < 50 lines
- Files < 800 lines
Tests
- All tests passing
- Coverage >= 80%
- Edge cases covered
- Error conditions tested
Security
- No hardcoded secrets
- Input validation present
- No SQL injection risks
- No XSS vulnerabilities
Build
- Build succeeds
- No warnings
- Bundle size acceptable
Verification Report
Summary
- Status: ✅ PASS / ❌ FAIL
- Score: X/Y checks passed
Details
| Check | Status | Notes |
|---|---|---|
| TypeScript | ✅/❌ | [details] |
| Lint | ✅/❌ | [details] |
| Tests | ✅/❌ | [details] |
| Coverage | ✅/❌ | XX% (target: 80%) |
| Build | ✅/❌ | [details] |
Action Items
[If FAIL, list what needs to be fixed]
NOTE: Verification loop should be run before every commit and PR.
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 First seen · 68 lines · 6 tokens per session scan A ccf5471cfdbd
verify is a command published in the GitHub repository Infopibe/everything-claude-code (8 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 398 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to verify, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.