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.
npx agentmods add commands/vertti/se-cove-claude-plugin/verifygit clone --depth 1 https://github.com/vertti/se-cove-claude-pluginWrote 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/vertti/se-cove-claude-plugin/verify)<a href="https://agentmods.dev/commands/vertti/se-cove-claude-plugin/verify"><img src="https://agentmods.dev/badge/commands/vertti/se-cove-claude-plugin/verify.svg" alt="Measured on agentmods" 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.00013 | $0.02218 |
| Opus 5 | $0.00006 | $0.01109 |
| Sonnet 5 | $0.00003 | $0.00444 |
| Haiku 4.5 | $0.00001 | $0.00222 |
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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/verify Command (Software Engineering)
FIRST: Check for Empty Input
If the user runs /verify with no question (empty arguments or only whitespace), OUTPUT the following help text directly to the user (copy it verbatim as your response), then STOP:
## /verify - Chain of Verification
Verify code, architecture, or bug fixes by checking against requirements, not implementation.
**Usage:**
/verify <question>
/verify --quick <question> # Fast check (haiku, 1 executor)
/verify --thorough <question> # Deep check (opus, 4+ executors)
/verify --focus=security <question> # Prioritize security tasks
**Options:**
| Flag | Short | Description |
|------|-------|-------------|
| --quick | -q | Fast verification, minimal depth |
| --thorough | -t | Comprehensive verification |
| --focus=X | -f X | Focus area: security, performance, api, testing, error-handling, style, scalability |
**Examples:**
- /verify How do I debounce in React?
- /verify --quick Is this null check right?
- /verify -t -f security Review the auth flow
**When to use:** Complex code, architecture decisions, bug investigations, API questions
**Skip for:** Typos, simple renames, obvious answers
Do NOT proceed with verification if no question was provided. Just output the help above.
Verify code, architecture decisions, and bug fixes using the Software Engineering Chain of Verification (SE-CoVe) pattern.
Usage
/verify <software engineering question or problem>
/verify --quick "Is this null check correct?"
/verify --thorough "Review this authentication flow"
/verify --focus=security "Analyze the login endpoint"
Command-Line Options
| Flag | Short | Description |
|---|---|---|
--quick |
-q |
Fast verification with minimal depth |
--thorough |
-t |
Comprehensive verification with maximum depth |
--focus=X |
-f X |
Prioritize a specific verification area |
| (no flags) | Standard verification (default) |
Focus Areas
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.
- 5d ago First seen · 242 lines · 13 tokens per session scan A 675051014d5f
verify is a command published in the GitHub repository vertti/se-cove-claude-plugin (20 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 2,218 once invoked, about $0.0001 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.
Other commands, from other repositories
logic-fix-all
Autonomous audit-and-fix — after consent, scan the target, fix every logic issue found (all severities), verify each fix, and report anything unresolved.
logic-diff
Check two code versions for semantic equivalence — use after a refactor or rewrite.
logic-explain
Trace execution step by step — use when code behavior is surprising or confusing.
logic-health
Sweep a whole codebase or directory for logic correctness — use before a release or to identify risk hotspots.
logic-locate
Locate the root cause of a confirmed failure — use when you have a stack trace, failing test, or wrong output.
logic-review
Review code for logic bugs — use when you suspect something is wrong but have no failing test yet.