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/fprochazka/claude-code-plugins/pre-plangit clone --depth 1 https://github.com/fprochazka/claude-code-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.00019 | $0.01205 |
| Opus 5 | $0.00010 | $0.00602 |
| Sonnet 5 | $0.00004 | $0.00241 |
| Haiku 4.5 | $0.00002 | $0.00120 |
Grade A, and why
pre-plan 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 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.
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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Planning Context Gathering
Gather everything needed to discuss a solution with the user, so a plan can be written afterward and then implemented. You are NOT writing a plan in this command, and you are NOT implementing anything. The output is a context briefing for discussion.
Scope
$ARGUMENTS
Phase 1 — Decide the source
Inspect the Scope above:
- Looks like a ticket ref (e.g.
ABC-1234, a Linear/GitHub/GitLab URL,#789): treat as ticket → run Phase 2. - Looks like a freeform problem description: skip Phase 2, use the description as the brief.
- Empty: use the current conversation context. If it's unclear what we're gathering context for, ask the user before proceeding.
Phase 2 — Read the ticket (only if a ticket ref was given)
Delegate to ONE subagent. Goal: load the full ticket and everything it transitively references.
The subagent must:
- Read title, description, and all comments.
- Inspect references, attachments, labels, project, status, links — anything rich.
- Follow links to related tickets, MRs/PRs, design docs, dashboards.
- If the ticket links to chat threads (Slack or similar) and they aren't already mirrored into ticket comments, read those threads too.
- Dump all findings into
./.claude/plans/pre-plan-<ticket-slug>-ticket.md(create the directory if missing) as a single markdown file. Include: full ticket content (title, description, all comments verbatim or near-verbatim where they carry real information), summarized linked context per link, a list of every concrete code/file/system reference found, and a list of any unresolved questions or ambiguities spotted in the ticket. - Return ONLY the path to that file (plus a 2-3 sentence high-level gist). Do NOT inline the full dump into the subagent's reply — the orchestrator will read the file as needed.
The subagent prompt must open with a skill-load instruction so it doesn't waste turns guessing CLI syntax. Resolve the tracker with the sdlc:team-workflow-identify skill first, then name the installed skill that covers that tracker: First, invoke the <skill-name> skill to load its usage guidance before running any commands.
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 · 77 lines · 19 tokens per session scan A ad5e5319b47b
pre-plan is a command published in the GitHub repository fprochazka/claude-code-plugins (11 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 1,205 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-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.