RapidSpec: Apply

A command for carrying out an approved RapidSpec change one task at a time.

In plain words
What is it for?
Use it to implement planned changes, review diffs before editing, stop safely, and mark completed tasks in tasks.md.
Why use it?
It keeps implementation work reviewable by showing each file change first, pausing at checkpoints, and keeping the task list accurate.

Command

Install

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.

agentmods
npx agentmods add commands/9j/rapidspec/apply
Clone the repo
git clone --depth 1 https://github.com/9j/RapidSpec
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,636 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.02636
Opus 5 $0.00008 $0.01318
Sonnet 5 $0.00003 $0.00527
Haiku 4.5 $0.00002 $0.00264

Measured yesterday against content hash ab701a948039, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

commands/apply.md · 378 lines

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:

  1. Update Main Branch

    git checkout main
    git pull origin main
    
  2. 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>"
    
  3. 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
    
  4. 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>
    

Read the full file on GitHub · 378 lines

Changes

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.

  1. yesterday First seen · 378 lines · 0 tokens per session scan A ab701a948039

Subscribe to this mod's changes

RapidSpec: Apply is a command published in the GitHub repository 9j/RapidSpec (5 stars, last pushed 9mo ago), licensed MIT. It adds 15 tokens to every session and 2,636 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.