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.
git 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/check)<a href="https://agentmods.dev/commands/racecraft-lab/paddock/check"><img src="https://agentmods.dev/badge/commands/racecraft-lab/paddock/check/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/racecraft-lab/paddock/check"><img src="https://agentmods.dev/badge/commands/racecraft-lab/paddock/check.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.00022 | $0.00435 |
| Opus 5.5 | $0.00009 | $0.00174 |
| Sonnet 5.5 | $0.00004 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
check 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
Project Health Check
Run a diagnostic scan of the current Spec Kit project to identify setup issues, missing artifacts, and configuration problems.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
-
Run diagnostic script: Execute
{SCRIPT}from the project root and review the output. -
Analyze results: The script checks 6 areas:
- Project structure —
.specify/,specs/,scripts/,templates/,memory/,constitution.md - AI agent configuration — detects which agent folder is present, verifies commands exist
- Feature specifications — lists features in
specs/, checks for spec.md/plan.md/tasks.md - Scripts health — verifies all bash and PowerShell scripts are present and executable
- Extensions health — validates extensions.yml and extension registry
- Git status — checks if inside a git repo, shows current branch
- Project structure —
-
Report findings: Present the diagnostic results to the user:
- Errors — things that are broken and need fixing
- Warnings — things that could cause problems
- Notes — informational items about the project state
-
Suggest fixes: For each error or warning found, suggest the specific command or action needed to resolve it. Common fixes include:
- Missing directories →
specify init --here - Missing constitution → copy from
templates/constitution-template.md - Missing feature artifacts → run
/speckit.planor/speckit.tasks - Non-executable scripts →
chmod +x scripts/bash/*.sh - Empty agent commands →
specify init --here --ai <agent>
- Missing directories →
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 · 43 lines · 22 tokens per session scan A 61bdfd62aa83
check is a command published in the GitHub repository racecraft-lab/Paddock (12 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 435 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-09-03.
Other commands, from other repositories
service-check
Request each agent to run a self-diagnostic to validate their runtime setup.
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.
fix
When /fix is invoked, immediately execute the following steps.
bug
Reproduce then TDD-fix a ready-for-agent bug ticket in this checkout. Web bugs get a browser repro first.
validate-prisma
Command: /validate-prisma Purpose: Quick Prisma query validation with comprehensive checks and auto-fix.
fix
Auto-fix all detected issues (short alias for comprehensive fixing).