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 skills/artttj/rapid-stack/plannpx skills add artttj/rapid-stack --skill plangit clone --depth 1 https://github.com/artttj/rapid-stackWhat 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.00034 | $0.00429 |
| Opus 5 | $0.00017 | $0.00215 |
| Sonnet 5 | $0.00007 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
plan 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.
What it actually says
op:plan
Think expensive, execute cheap: plan at high effort so the build can run lean.
Steps
-
Locate the spec: the argument, else the newest
docs/specs/*/spec.mdwithstatus: approved. Hard stop if not approved or Open questions is non-empty — route back to /op:spec. -
Effort check: suggest max for this step (arrow-choice).
-
Compute the spec pin (body = everything after the closing frontmatter
---):awk 'c==2{print} /^---$/{if(c<2)c++}' docs/specs/<slug>/spec.md | shasum -a 256 | cut -c1-12 -
Write
docs/specs/<slug>/plan.md:
---
spec: docs/specs/<slug>/spec.md
spec-version: <12-hex pin>
status: draft
---
# <title> — build plan
## Tasks
### Task 1: <name>
- Files: exact paths to create or modify
- Tests: the failing test to write first, named from the spec's Tests section
- Steps: write test → see it fail → implement → see it pass → commit
(one section per task; every spec Behavior maps to a task; every task ends committable)
- Self-check against the spec: every Behavior covered, no placeholders, exact paths. Fix inline.
- Sign-off gate (arrow-choice): sign off / revise / abandon. On sign-off →
status: signed-off, commit (docs: add <slug> plan), offer /op:build. - Re-run: /op:plan on a spec that already has a plan regenerates plan.md fresh (new pin). It never edits the spec.
Proof at end: plan path, pin value, status.
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 · 43 lines · 34 tokens per session scan A 8ef4aa2366f5
plan is a skill published in the GitHub repository artttj/rapid-stack (2 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 429 once invoked, about $0.0002 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 skills, from other repositories
autopilot
Full autonomous execution from idea to working code.
plannotator-annotate
Open Plannotator's annotation UI for a file, folder, or URL, then address the returned annotations.
statistical-power
Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers…
chase-travel
Search Chase UR travel portal via Patchright for cash prices, points pricing, Points Boost offers, and Chase Edit hotel benefits. Use for pay-with-points portal comparison on Sapphire Reserve/Preferred.
points-valuations
Cents-per-point (cpp) valuations across major loyalty programs from four publications. Floor/ceiling rules for deciding if a redemption is good or exceptional.
awardwallet
Query AwardWallet for loyalty program balances, elite status, and transaction history. Use when checking points inventory, airline status, or planning trips on points.