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/archive)<a href="https://agentmods.dev/commands/9j/rapidspec/archive"><img src="https://agentmods.dev/badge/commands/9j/rapidspec/archive/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/archive"><img src="https://agentmods.dev/badge/commands/9j/rapidspec/archive.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.00013 | $0.01508 |
| Opus 5.5 | $0.00005 | $0.00603 |
| Sonnet 5.5 | $0.00003 | $0.00302 |
| Haiku 4.5 | $0.00001 | $0.00151 |
Grade A, and why
RapidSpec: Archive 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archive RapidSpec Change
<command_purpose> Archive completed RapidSpec changes and merge spec deltas to canonical specs. Move to timestamped archive, validate strictly, close linked Linear issues. </command_purpose>
<change_id> #$ARGUMENTS </change_id>
<critical_requirement> MUST verify all tasks completed before archiving. MUST validate canonical specs after delta merge. MUST rollback if validation fails. CAN auto-close linked Linear issues when found. </critical_requirement>
Quick Archive (CLI Option)
Basic archive with CLI (no spec merging):
# Simple timestamp + move to archive
rapid archive <change-id>
# Skip validation check
rapid archive <change-id> --skip-validation
This CLI command only:
- Checks task completion (warns if incomplete)
- Generates Supabase timestamp (YYYYMMDDhhmmss)
- Moves to archive directory
For full spec delta merging, Linear closing, and validation, continue with Main Tasks below.
Main Tasks
1. Verify Completion (ALWAYS FIRST)
Completion checklist:
- Check all tasks in tasks.md marked
[x] - Verify code committed to git
- Ensure tests passing
- If incomplete, list remaining tasks and abort
2. Archive with Timestamp
Actions:
- Generate timestamp:
date +%Y%m%d%H%M%S(Supabase format) - Move
rapidspec/changes/<change-id>/→rapidspec/changes/archive/<timestamp>-<change-id>/ - Example:
20251111123045-prevent-duplicate-smartlinks
3. Merge Spec Deltas
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 · 242 lines · 0 tokens per session scan A 0e130ed7668d
RapidSpec: Archive is a command published in the GitHub repository 9j/RapidSpec (5 stars, last pushed 11mo ago), licensed MIT. It adds 13 tokens to every session and 1,508 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
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
doc-changelog
Generation and maintenance of the project changelog.