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/ihorkatkov/pantheon/create-plangit clone --depth 1 https://github.com/ihorkatkov/pantheonWrote 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/ihorkatkov/pantheon/create-plan)<a href="https://agentmods.dev/commands/ihorkatkov/pantheon/create-plan"><img src="https://agentmods.dev/badge/commands/ihorkatkov/pantheon/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.00031 | $0.03609 |
| Opus 5 | $0.00015 | $0.01804 |
| Sonnet 5 | $0.00006 | $0.00722 |
| Haiku 4.5 | $0.00003 | $0.00361 |
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 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.
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:<port>/api/new-endpoint` How it starts
The opening of the file, as written. The whole thing — 487 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.
CRITICAL:
- DO NOT do any research, use file specified from the user. If it's not provided, ask the user to provide it.
- DO NOT create any timelines or milestones.
- DO NOT complement choices made by the user: no "Excellent choice", "Great point", or "Very smart", just stick to practical facts and make only relevant observations.
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
- FIRST: Check if a spec file exists (
thoughts/tasks/task-name/spec.md) and read it FULLY - Then read the task file and any other 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. Link to the spec file if it exists (`thoughts/tasks/task-name/spec.md`)
3. Any relevant context, constraints, or specific requirements
4. Links to related research or previous implementations
5. Use the "guided discovery" method
I'll analyze this information and work with you to create a comprehensive plan.
Tip: You can also invoke this command with a spec or task file directly:
- `/create-plan thoughts/tasks/task-name/spec.md`
- `/create-plan thoughts/tasks/task-name/task.md`
For deeper analysis, try: `/create-plan think deeply about thoughts/tasks/task-name/spec.md`
- "guided discovery" method When the "guided discovery" method is selected by the user: Act as a principal engineer using the "guided discovery" method. Your goal is to help me create a robust technical implementation plan.
- Ask probing, open-ended questions, one at a time.
- Before every question, you should explore the codebase to do research, and consider doing a web search.
- Your questions should force me to think critically about all aspects of the plan.
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 · 487 lines · 31 tokens per session scan A 8f5181da2e95
create-plan is a command published in the GitHub repository ihorkatkov/pantheon (5 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 3,609 once invoked, about $0.0002 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.