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/hoblin/claude-ruby-marketplace/create_plangit clone --depth 1 https://github.com/hoblin/claude-ruby-marketplaceWrote 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/hoblin/claude-ruby-marketplace/create_plan)<a href="https://agentmods.dev/commands/hoblin/claude-ruby-marketplace/create_plan"><img src="https://agentmods.dev/badge/commands/hoblin/claude-ruby-marketplace/create_plan.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.00009 | $0.03358 |
| Opus 5 | $0.00005 | $0.01679 |
| Sonnet 5 | $0.00002 | $0.00672 |
| Haiku 4.5 | $0.00001 | $0.00336 |
Grade A, and why
create_plan scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- [ ] API endpoint returns 200: `curl localhost:8080/api/new-endpoint` How it starts
The opening of the file, as written. The whole thing — 459 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Plan
You are tasked with creating detailed implementation plans through an interactive, iterative process. You should be skeptical, thorough, and work collaboratively with the user to produce high-quality technical specifications.
Initial Response
When this command is invoked:
-
Check if parameters were provided:
- If a file path or ticket reference was provided as a parameter, skip the default message
- Immediately read any provided files FULLY
- Begin the research process
-
If no parameters provided, respond with:
I'll help you create a detailed implementation plan. Let me start by understanding what we're building.
Please provide:
1. The task/ticket description (or reference to a ticket file)
2. Any relevant context, constraints, or specific requirements
3. Links to related research or previous implementations
I'll analyze this information and work with you to create a comprehensive plan.
Tip: You can also invoke this command with a ticket file directly: `/rpi:create_plan ./thoughts/username/tickets/eng_1234.md`
For deeper analysis, try: `/rpi:create_plan think deeply about ./thoughts/username/tickets/eng_1234.md`
Then wait for the user's input.
Process Steps
Step 1: Context Gathering & Initial Analysis
-
Read all mentioned files (if any) immediately and FULLY:
- Ticket files (e.g.,
./thoughts/username/tickets/eng_1234.md) - Research documents
- Related implementation plans
- Any JSON/data files mentioned
- IMPORTANT: Use the Read tool WITHOUT limit/offset parameters to read entire files
- CRITICAL: If files mentioned, DO NOT spawn sub-tasks before reading these files yourself in the main context
- NEVER read files partially - if a file is mentioned, read it completely
- Ticket files (e.g.,
-
Gather Historical Context: Spawn
rpi:thoughts-analyzerwith ticket reference, title, description, and acceptance criteria.DO NOT proceed to step 3 until this subagent returns. Its output is required input for step 3.
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.
- 4d ago First seen · 459 lines · 9 tokens per session scan A 8f064d7f7cca
create_plan is a command published in the GitHub repository hoblin/claude-ruby-marketplace (37 stars, last pushed 25d ago), licensed MIT. It adds 9 tokens to every session and 3,358 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
sm-buff
You usually don't run buff directly — run sm sail. sm sail drives the whole PR to green and calls buff watch / triage for you, stopping only when it needs you to act (see /sm-sail). Reach for sm buff here only for surgical work: inspecting a specific failure, or resolving a single review thread when sail has parked on…
document-project
Document brownfield projects for AI context. Use when the user says ""document this project"" or ""generate project docs"".
sm-swab
Run slop-mop's iterative development loop for this repository.
create-architecture
Create architecture solution design decisions for AI agent consistency. Use when the user says ""lets create architecture"" or ""create technical architecture"" or ""create a solution design"".
quick-spec
Very quick process to create implementation-ready quick specs for small changes or features. Use when the user says ""create a quick spec"" or ""generate a quick tech spec"".
create-prd
Create a PRD from scratch. Use when the user says ""lets create a product requirements document"" or ""I want to create a new PRD"".