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/xiaolai/cc-suite/verifygit clone --depth 1 https://github.com/xiaolai/cc-suiteWhat 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.00010 | $0.00987 |
| Opus 5 | $0.00005 | $0.00494 |
| Sonnet 5 | $0.00002 | $0.00197 |
| Haiku 4.5 | $0.00001 | $0.00099 |
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 2d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Model & Settings Selection
Follow the instructions in commands/shared/model-selection.md to discover available models and present choices.
- Recommended model: second available from preflight (verification needs less power). If only one model is available, use it.
- Recommended reasoning effort:
medium - Include sandbox question: No (verification always uses
read-only)
Workflow
CRITICAL: This command verifies fixes from a PREVIOUS audit. It does NOT discover new findings.
Step 1: Input Parsing
$ARGUMENTS should contain or reference the previous audit report:
- If empty: Look for recent
audit-*.mdfile in current directory - If file path: Read that audit report
- If contains "Critical Findings": Use as inline report
If no audit report found:
No previous audit report found.
Options:
1. Run /audit first to generate baseline
2. Provide report: /verify audit-2025-11-18.md
3. Paste inline: /verify [audit report text]
And STOP.
Note: The audit report may contain 5 dimensions (mini audit) or 9 dimensions (full audit). Verify only the dimensions that appear in the report.
Step 2: Verify with Codex
Follow commands/shared/codex-call.md for the call pattern (CLI runner).
- Command persona: "You are a verification auditor. Only check findings from a previous audit report."
- Sandbox:
read-only - Approval-policy:
never
prompt: "Your ONLY job is to confirm fixes from a previous audit.
## Previous Audit Report
{AUDIT_REPORT_CONTENT}
## Your Mission
1. **Extract Finding Checklist by Dimension**:
Parse all findings organized by whatever dimensions appear in the audit report.
Full audits have 9 dimensions; mini audits have 5. Only verify what's present.
2. **Verify Each Finding**:
For each finding from the report:
- Read the file at the exact location
- Check if the finding still exists
- Mark status:
- FIXED — Finding resolved, no new problems introduced
- NOT FIXED — Finding still present
- PARTIAL — Partially addressed
- MOVED — Code relocated, verify new location
3. **Quick Spot Check** (5 min max):
- Only check files that were modified
- Look for syntax errors, broken imports, type errors, or runtime exceptions introduced by fixes
- DO NOT run comprehensive scan
## Requirements
- ONLY verify findings from the audit report
- Do NOT discover new findings systematically
- Be fast (2-10 minutes)
- Clear pass/fail per finding"
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.
- 2d ago First seen · 141 lines · 10 tokens per session scan A b7031c316224
verify is a command published in the GitHub repository xiaolai/cc-suite (44 stars, last pushed 24d ago), licensed ISC. It adds 10 tokens to every session and 987 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.