Borrowing it
Nothing to install: this file belongs to Benkapner/claude-code-basecamp. 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/Benkapner/claude-code-basecamp/main/.claude/commands/verify.mdgit clone --depth 1 https://github.com/Benkapner/claude-code-basecampWrote 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/benkapner/claude-code-basecamp/verify)<a href="https://agentmods.dev/commands/benkapner/claude-code-basecamp/verify"><img src="https://agentmods.dev/badge/commands/benkapner/claude-code-basecamp/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/benkapner/claude-code-basecamp/verify"><img src="https://agentmods.dev/badge/commands/benkapner/claude-code-basecamp/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.00029 | $0.00192 |
| Opus 5.5 | $0.00012 | $0.00077 |
| Sonnet 5.5 | $0.00006 | $0.00038 |
| Haiku 4.5 | $0.00003 | $0.00019 |
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.
What it actually says
Verify Command
Use the Skill tool to invoke verification-loop explicitly, then run Phases 1-4 only:
- Environment check
- Type check
- Lint check
- Test suite
If the Skill tool is not available or the skill is not found, run the checks directly using the commands from each phase (see the verification-loop skill for exact commands).
Report results. Do NOT run code review (Phase 5) or security scan (Phase 6) — Phase 6 is for /quality-gate.
Arguments
$ARGUMENTS can be:
quick— Only phases 2-3 (types + lint, skip tests)full— Phases 1-4 (default)
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 · 22 lines · 29 tokens per session scan A 394c52afbfb2
verify is a command published in the GitHub repository Benkapner/claude-code-basecamp (18 stars, last pushed 27d ago), licensed MIT. It adds 29 tokens to every session and 192 once invoked, about $0.0001 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 commands, from other repositories
audit
Use when auditing existing project docs for quality, completeness, and code alignment — generates findings report with fix recommendations.
critique
Design lens critique covering visual hierarchy, clarity, and anti-slop patterns — produces a findings table, no code edits unless asked. Use when the user wants a design review, says "what's wrong with this UI", or needs a second opinion before a handoff or presentation.
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.
cc-review
(Conductor) Review code changes against spec and standards.
fix-comments
Address PR review comments by implementing requested changes automatically.
review-open-prs
Command "review-open-prs" from The-Artificer-of-Ciphers-LLC/skills-from-the-artificer, covering batch pr review directive — all open prs i did not author, phase a — enumerate target prs & build the queue, phase b — per-pr directive (runs once per queued $pr), 0. context anchoring and 1. preconditions.