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/9j/rapidspec/commitgit clone --depth 1 https://github.com/9j/RapidSpecWhat 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.00014 | $0.01799 |
| Opus 5 | $0.00007 | $0.00899 |
| Sonnet 5 | $0.00003 | $0.00360 |
| Haiku 4.5 | $0.00001 | $0.00180 |
Grade A, and why
RapidSpec: Commit 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 yesterday.
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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit RapidSpec Implementation
<command_purpose> Create conventional commits with task verification and discovered work capture. Verify git changes match tasks.md before marking complete, support partial commits. </command_purpose>
<critical_requirement>
MUST verify claims with git diff and git status - NEVER trust memory.
MUST match actual git changes to tasks.md before marking complete.
MUST capture discovered work (unplanned improvements).
CAN commit partial work for incremental progress.
</critical_requirement>
Main Tasks
1. Review Git Changes (ALWAYS FIRST)
Immediate Actions:
git status
git diff
git log --oneline -5
- List all modified, added, deleted files
- Analyze actual code changes
- Check recent commit messages for style
2. Match Changes to Tasks
Task verification process:
- Read
rapidspec/changes/<change-id>/tasks.md - For each task, check if actual git changes match:
- Task 1.1: Database Migration → Check migrations/ folder
- Task 1.2: API Validation → Check API route files
- Task 1.3: UI Toast → Check component files
- Mark matching tasks as
[x] - Leave incomplete tasks as
[ ] - Capture discovered work not in original tasks
3. Update tasks.md
Actions:
- Update checkboxes:
[ ]→[x]for completed tasks - Add "Discovered Tasks" section if unplanned work found
- Show completion status: "5/6 tasks complete"
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.
- yesterday First seen · 294 lines · 0 tokens per session scan A d6d4626765c0
RapidSpec: Commit is a command published in the GitHub repository 9j/RapidSpec (5 stars, last pushed 9mo ago), licensed MIT. It adds 14 tokens to every session and 1,799 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-31.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.