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/slbug/claude-ruby-grape-rails/brainstormnpx skills add slbug/claude-ruby-grape-rails --skill brainstormgit clone --depth 1 https://github.com/slbug/claude-ruby-grape-railsWrote 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/skills/slbug/claude-ruby-grape-rails/brainstorm)<a href="https://agentmods.dev/skills/slbug/claude-ruby-grape-rails/brainstorm"><img src="https://agentmods.dev/badge/skills/slbug/claude-ruby-grape-rails/brainstorm.svg" alt="Measured on agentmods" 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 | $0.00039 | $0.01985 |
| Opus 5 | $0.00019 | $0.00992 |
| Sonnet 5 | $0.00008 | $0.00397 |
| Haiku 4.5 | $0.00004 | $0.00198 |
Grade A, and why
rb:brainstorm 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 3d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm
Adaptive requirements gathering before planning. Produces an interview.md
that /rb:plan consumes to skip clarification.
Workflow
/rb:brainstorm {topic}
|
v
[INTERVIEW] <───────────────────┐
| |
v (sufficient OR user exit) |
[DECISION POINT] |
├─ Research ──> [RESEARCH] ──┘
├─ Continue interview ───────┘
├─ Make a plan ──> STOP (suggest /rb:plan .claude/plans/{slug}/interview.md)
├─ Store & exit ──> STOP (artifacts saved)
└─ Discuss ──> freeform ──> [DECISION POINT]
STEP 0: Read the interview playbook before starting
Read ${CLAUDE_SKILL_DIR}/references/interview-techniques.md. Apply
its codebase-scan patterns, scan-depth rules, and signal-detection
rubrics as the canonical interview cadence.
Phase 1: Adaptive Interview
Ask ONE question at a time. Track coverage across 6 dimensions:
| Dimension | Target | Sufficient | Score |
|---|---|---|---|
| What | Specific behavior/features | Concrete verbs, not vague | 0-2 |
| Why | Problem solved, user need | Clear benefit stated | 0-2 |
| Scope | In/out boundaries | Explicit exclusions | 0-2 |
| Where | Modules, contexts, files | Paths or context names | 0-2 |
| How | Approach, constraints | At least one constraint | 0-2 |
| Edge | Error states, scale, auth | 2+ edge cases identified | 0-2 |
Scoring: 0 = uncovered, 1 = partial ("maybe some caching"), 2 = sufficient ("Redis cache for session tokens, 15min TTL").
Interview sufficient when total score >= 8 out of 12 and every dimension has at least a score of 1.
Question Order
- What — almost always first
- Why — understand motivation before narrowing
- Scope — ask within first 3-4 questions, especially for "optimize X" topics
- Where/How/Edge — order by lowest coverage, informed by codebase scans
Between-Question Codebase Scans
Before each question after the first, run a brief codebase scan with Grep/Glob
based on what the user just said. See references/interview-techniques.md for
the scan pattern table.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 199 lines · 39 tokens per session scan A 743a217791f9
rb:brainstorm is a skill published in the GitHub repository slbug/claude-ruby-grape-rails (7 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 1,985 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
pinme-email
Use this skill when a PinMe project (Worker TypeScript) needs to integrate email sending (sendemail). Guides AI to generate correct Worker TS code.
goai
GoAI is a Go SDK for AI applications. One unified API across 25+ LLM providers. Inspired by the Vercel AI SDK, adapted to Go idioms (generics, interfaces, channels).
verify
Self-healing verification loop (test → clippy → fmt).
rust-project-validate
运行 cargo fmt/clippy/build/e2e/test 验证项目规范；在每次任务结束前必须调用，重要的是必须在端到端测试之后执行，为提交代码做最后准备.
rust-review
Rust 服务审查：panic、SQL 注入、密钥、错误吞没、遗留标记.
python-services
Python patterns for CLI tools, async concurrency, and backend services. Use when working with Python code, building CLI apps, FastAPI services, async with asyncio, background jobs, or configuring uv, ruff, ty, pytest, or pyproject.toml.