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/9j/RapidSpecWrote 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/9j/rapidspec/apply)<a href="https://agentmods.dev/commands/9j/rapidspec/apply"><img src="https://agentmods.dev/badge/commands/9j/rapidspec/apply/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/9j/rapidspec/apply"><img src="https://agentmods.dev/badge/commands/9j/rapidspec/apply.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.00015 | $0.02636 |
| Opus 5.5 | $0.00006 | $0.01054 |
| Sonnet 5.5 | $0.00003 | $0.00527 |
| Haiku 4.5 | $0.00002 | $0.00264 |
Grade A, and why
RapidSpec: Apply 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.
How it starts
The opening of the file, as written. The whole thing — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply RapidSpec Implementation
<command_purpose> Implement RapidSpec proposals step-by-step with checkpoint-based workflow. Each task is testable and allows direction changes at any checkpoint. </command_purpose>
<change_id> #$ARGUMENTS </change_id>
<critical_requirement>
MUST show diffs before every file change. No exceptions.
MUST stop immediately when user says "wait" or "stop".
MUST update tasks.md after completing each task (change - [ ] to - [x]).
NEVER implement multiple tasks without checkpoints between them.
NEVER mark tasks complete without actually implementing them.
</critical_requirement>
Environment Setup (Optional)
Git Worktree Setup:
-
Update Main Branch
git checkout main git pull origin main -
Create Feature Branch and Worktree
# Get git root directory git_root=$(git rev-parse --show-toplevel) # Create worktrees directory mkdir -p "$git_root/.worktrees" # Add to .gitignore if not already there if ! grep -q "^\.worktrees$" "$git_root/.gitignore"; then echo ".worktrees" >> "$git_root/.gitignore" fi # Create worktree with feature branch # Branch name example: feature/add-duplicate-prevention git worktree add -b feature/<change-id> "$git_root/.worktrees/<change-id>" main # Change to worktree directory cd "$git_root/.worktrees/<change-id>" -
Verify Environment
# Confirm in correct directory pwd git branch --show-current # Install dependencies if needed npm install # or pnpm install, yarn, etc. # Run initial tests to ensure clean state npm test -
Cleanup After Merge (when change is complete)
# Go back to main directory cd "$git_root" # Remove worktree git worktree remove .worktrees/<change-id> # Delete feature branch (if merged) git branch -d feature/<change-id>
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 · 378 lines · 0 tokens per session scan A ab701a948039
RapidSpec: Apply is a command published in the GitHub repository 9j/RapidSpec (5 stars, last pushed 11mo ago), licensed MIT. It adds 15 tokens to every session and 2,636 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-08-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.