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/jeffh/claude-plugins/create_plangit clone --depth 1 https://github.com/jeffh/claude-pluginsWhat 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.03236 |
| Opus 5 | $0.00005 | $0.01618 |
| Sonnet 5 | $0.00002 | $0.00647 |
| Haiku 4.5 | $0.00001 | $0.00324 |
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 2d 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` Copies of this mod
2 near-identical copies found in the catalogue:
- create_plan_nt — 95% identical, 24 lines differ
- create_plan_generic — 92% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 444 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: `/create_plan thoughts/allison/tickets/eng_1234.md`
For deeper analysis, try: `/create_plan think deeply about thoughts/allison/tickets/eng_1234.md`
Then wait for the user's input.
Process Steps
Step 1: Context Gathering & Initial Analysis
-
Read all mentioned files immediately and FULLY:
- Ticket files (e.g.,
thoughts/allison/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: 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.,
-
Spawn initial research tasks to gather context: Before asking the user any questions, use specialized agents to research in parallel:
- Use the codebase-locator agent to find all files related to the ticket/task
- Use the codebase-analyzer agent to understand how the current implementation works
- If relevant, use the thoughts-locator agent to find any existing thoughts documents about this feature
- If a Linear ticket is mentioned, use the linear-ticket-reader agent to get full details
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.
- 2d ago First seen · 444 lines · 9 tokens per session scan A 12d86465e10c
create_plan is a command published in the GitHub repository jeffh/claude-plugins (12 stars, last pushed 18d ago), licensed Apache-2.0. It adds 9 tokens to every session and 3,236 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.