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 skills add racecraft-lab/Paddock --skill speckit-cleanup-rungit 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/skills/racecraft-lab/paddock/speckit-cleanup-run)<a href="https://agentmods.dev/skills/racecraft-lab/paddock/speckit-cleanup-run"><img src="https://agentmods.dev/badge/skills/racecraft-lab/paddock/speckit-cleanup-run/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/skills/racecraft-lab/paddock/speckit-cleanup-run"><img src="https://agentmods.dev/badge/skills/racecraft-lab/paddock/speckit-cleanup-run.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.00037 | $0.03819 |
| Opus 5 | $0.00018 | $0.01910 |
| Sonnet 5 | $0.00007 | $0.00764 |
| Haiku 4.5 | $0.00004 | $0.00382 |
Grade A, and why
speckit-cleanup-run 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 9d 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:
- speckit-cleanup — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 479 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
Perform a final quality gate after implementation. Review all changes made during implementation, identify technical debt, and handle issues according to severity:
- Small issues: Fix immediately (Scout Rule) - with user confirmation
- Medium issues: Create follow-up tasks in tasks.md
- Large issues: Generate detailed analysis with options in tech-debt-report.md
Operating Constraints
Constitution Authority: The project constitution (.specify/memory/constitution.md) is non-negotiable. Any cleanup action that would violate constitution principles is forbidden. If a fix would conflict with a MUST principle, escalate to large issue instead of fixing.
Linter Deference: For style and formatting issues, defer to the project's configured linters. Do NOT manually fix issues that linters should handle - instead, run the linter with auto-fix if available.
Preserve User Intent: If code appears intentional (e.g., commented code with explanation, disabled tests with TODO reason), do NOT auto-fix. Escalate to medium issue for user review.
Execution Steps
1. Initialize Cleanup Context
Run .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks once from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS. Derive absolute paths:
- SPEC = FEATURE_DIR/spec.md
- PLAN = FEATURE_DIR/plan.md
- TASKS = FEATURE_DIR/tasks.md
- CONSTITUTION = .specify/memory/constitution.md
- TECH_DEBT_REPORT = FEATURE_DIR/tech-debt-report.md
Abort with error if TASKS does not exist or has no completed tasks (implementation not run). 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 Implementation Context
Load minimal necessary context from each artifact:
From tasks.md:
- All completed tasks (marked
[X]or[x]) - File paths mentioned in completed tasks
- Implementation phases that were executed
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.
- 9d ago First seen · 479 lines · 37 tokens per session scan A ff83ba0dac03
speckit-cleanup-run is a skill published in the GitHub repository racecraft-lab/Paddock (11 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 3,819 once invoked, about $0.0002 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 skills, from other repositories
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
improve
Autonomous quality improvement loop. Scores a target against a rubric, selects the highest-leverage axis, attacks it, verifies, documents, and loops. No pre-planning between iterations — each loop re-scores from scratch.
code-review-pipeline
Multi-dimensional code review across correctness, security, performance, and maintainability with confidence-gated reporting and remediation loops.
verification
Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.