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/artttj/rapid-stack/brngit 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.00015 | $0.00305 |
| Opus 5 | $0.00008 | $0.00152 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
brn 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
Use the superpowers:brainstorming skill on the request below, but with these binding overrides (these are user instructions and take precedence over the skill's checklist):
- Skip step 6 (do not write a spec doc)
- Skip steps 7–8 (no spec self-review, no spec review gate)
- Skip step 9 (do not invoke
writing-plans) - Cap clarifying questions at 5 — pick the highest-signal ones
- Present the design verbally only; do not propose creating any file
After the user approves the verbal design, add one final section: Recommended execution. In that section, propose the concrete next move:
- Which agent to dispatch (e.g.,
code-reviewer,tdd-guide,feature-dev:code-architect,general-purposefor parallel exploration) - Whether the work fits a single agent, parallel subagents, or
subagent-driven-development - Whether to open a git worktree first
- Which skill to chain into next (
tdd-workflow,executing-plans, etc.)
Pick one path and recommend it explicitly. Don't list every option neutrally.
If superpowers:brainstorming is not installed, run a 3-question Socratic dialogue, propose 2 approaches with the recommended one first, then add the Recommended execution section.
$ARGUMENTS
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 · 25 lines · 15 tokens per session scan A 37c419fe6b53
brn is a command published in the GitHub repository artttj/rapid-stack (2 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 305 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
psm
/oh-my-claudecode:psm is a compatibility alias for /oh-my-claudecode:project-session-manager.
plan-review
The core plan review flow across Claude Code, Codex, and other supported agent hosts.
release
Ship a stable cmux release built by CI: bump version, update changelog, open a PR, merge, tag, then GitHub Actions builds, signs, and publishes.
refresh-compare-pages
Freshly research, add, and refresh marketing compare pages, then open a descriptive PR.
step-research
Always research before proposing a fix. The Untether bug you're chasing is often a known upstream engine quirk, a previously-fixed regression, or a documented config gotcha.
self-improve
This compatibility command keeps /oh-my-claudecode:self-improve available without loading the full self-improve skill description in every Claude Code session.