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/racecraft-lab/paddock/verifygit clone --depth 1 https://github.com/racecraft-lab/PaddockWrote 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/racecraft-lab/paddock/verify)<a href="https://agentmods.dev/commands/racecraft-lab/paddock/verify"><img src="https://agentmods.dev/badge/commands/racecraft-lab/paddock/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.00027 | $0.02047 |
| Opus 5 | $0.00014 | $0.01024 |
| Sonnet 5 | $0.00005 | $0.00409 |
| Haiku 4.5 | $0.00003 | $0.00205 |
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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- verify — 95% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Goal
Validate the implementation against its specification artifacts (spec.md, plan.md, tasks.md, constitution.md). This command MUST run only after /speckit.implement has completed.
Operating Constraints
STRICTLY READ-ONLY: Do not modify any files. Output a structured analysis report. Offer an optional remediation plan (user must explicitly approve before any follow-up editing commands would be invoked manually).
Constitution Authority: The project constitution (.specify/memory/constitution.md) is non-negotiable within this verification scope. Constitution conflicts are automatically CRITICAL and require adjustment of the spec, plan, tasks or implementation—not dilution, reinterpretation, or silent ignoring of the principle. If a principle itself needs to change, that must occur in a separate, explicit constitution update outside /speckit.verify.run.
Execution Steps
1. Initialize Verification Context
Run {SCRIPT} from repo root.
- Script succeeds (on a feature branch): Parse JSON for FEATURE_DIR. Set
FEATURE_BRANCH = true. Proceed to next step. - Script fails (not on a feature branch): You MUST prompt for available features (Scan
specs/NNN-*/to get available features). Use the AskUserQuestion tool to let the user select. Do NOT guess or auto-select a change. Always let the user choose.
Derive absolute paths:
- SPEC = FEATURE_DIR/spec.md
- PLAN = FEATURE_DIR/plan.md
- TASKS = FEATURE_DIR/tasks.md.
Abort if any required file is missing (instruct the user to run missing prerequisite command). For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").
2. Load Configuration
Run the load-config script (.specify/extensions/verify/scripts/bash/load-config.sh or .specify/extensions/verify/scripts/powershell/load-config.ps1) from the repo root. Parse the max_findings value from its output and store it for use in Step 6. If the script fails, abort and relay its error message to the user.
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.
- 3d ago First seen · 215 lines · 27 tokens per session scan A c457079158c5
verify is a command published in the GitHub repository racecraft-lab/Paddock (11 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 2,047 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-09-03.
Other commands, from other repositories
review
Review code changes against project conventions.
gh-triage
GitHub OSS maintainer lifecycle triage, review, and approval management.
codebase-review
Review an entire codebase for architecture, engineering health, and exploitable risk; generate a prioritized remediation plan, an evidence-anchored system knowledge document, or both.
afe
Evaluate feature - code review or comparison (shortcut for feature-eval).
factory-ticket
Implement exactly one already-claimed Linear ticket in the current worktree.
Hexagonal.Gatekeeper
Your role is to perform a deep, architecture-focused code review on a specific branch. You must validate that all changes strictly follow Hexagonal Architecture (Ports & Adapters) principles and align with the existing codebase patterns.