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/triagegit 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.00018 | $0.02820 |
| Opus 5 | $0.00009 | $0.01410 |
| Sonnet 5 | $0.00004 | $0.00564 |
| Haiku 4.5 | $0.00002 | $0.00282 |
Grade A, and why
RapidSpec: Triage 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage RapidSpec Review Findings
<command_purpose> Present review findings one by one for triage. Allows individual judgment on which issues to fix now, defer, or skip. Converts accepted findings into actionable tasks in tasks.md. </command_purpose>
IMPORTANT: DO NOT CODE ANYTHING DURING TRIAGE!
This command is for:
- Triaging code review findings from
/rapid:review - Converting important findings into tasks
- Prioritizing issues by severity
- Deferring low-priority improvements
<change_id> #$ARGUMENTS </change_id>
<critical_requirement> MUST present findings one by one, not in batch. MUST wait for user decision before proceeding to next finding. MUST update tasks.md when user accepts a finding. NEVER implement fixes during triage - only track them. </critical_requirement>
Main Tasks
1. Read Review Context (ALWAYS FIRST)
Immediate Actions:
- Read
rapidspec/changes/<change-id>/proposal.md- Understand scope - Check if review findings exist (from previous
/rapid:reviewrun) - Read
rapidspec/changes/<change-id>/tasks.md- Current task list
2. Present Each Finding
Presentation Format:
┌─────────────────────────────────────────────────────────┐
│ Triage Progress: X/Y findings | Est. Z min remaining │
└─────────────────────────────────────────────────────────┘
---
Finding #N: [Brief Title]
Severity: 🔴 P1 (CRITICAL) / 🟡 P2 (IMPORTANT) / 🔵 P3 (NICE-TO-HAVE)
Category: [Security/Performance/Architecture/Quality/Testing/etc.]
Description:
[Detailed explanation of the issue or improvement]
Location: [file_path:line_number]
Problem:
[What's wrong or could be better]
Impact:
[Why this matters, what could happen if not fixed]
Proposed Solution:
[How to fix it - specific actionable steps]
Estimated Effort: Small (< 30min) / Medium (30min-2h) / Large (> 2h)
---
Add to tasks?
1. yes - add to tasks.md as new task
2. next - skip this finding
3. custom - modify severity/description before adding
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 · 439 lines · 0 tokens per session scan A d1107f54ebf8
RapidSpec: Triage is a command published in the GitHub repository 9j/RapidSpec (5 stars, last pushed 9mo ago), licensed MIT. It adds 18 tokens to every session and 2,820 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.