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/jimmc414/claude-code-plugin-marketplace/collaborative-plangit clone --depth 1 https://github.com/jimmc414/claude-code-plugin-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/jimmc414/claude-code-plugin-marketplace/collaborative-plan)<a href="https://agentmods.dev/commands/jimmc414/claude-code-plugin-marketplace/collaborative-plan"><img src="https://agentmods.dev/badge/commands/jimmc414/claude-code-plugin-marketplace/collaborative-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.00011 | $0.00389 |
| Opus 5 | $0.00005 | $0.00195 |
| Sonnet 5 | $0.00002 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
collaborative-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 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.
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.
What it actually says
Collaborative Planning Session
You are entering a collaborative planning session with the user. This is an iterative requirements gathering and planning workflow.
Phase 1: Requirements Gathering (Iterative Q&A)
Begin by understanding what the user wants to accomplish through iterative questioning:
- Use the AskUserQuestion tool to ask clarifying questions about the task
- You may ask up to 4 questions per round (this is the tool's limit)
- IMPORTANT: Always include this option in every question round:
- Label: "Done - ready to plan"
- Description: "I have no more questions, proceed to planning"
- After receiving answers, analyze the responses
- If the user did NOT select "Done - ready to plan", continue asking follow-up questions using AskUserQuestion again
- Repeat this loop until the user selects "Done - ready to plan"
Guidelines for questions:
- Ask about goals, constraints, preferences, and edge cases
- Prioritize the most important unknowns first
- Build on previous answers with deeper follow-up questions
- Cover technical requirements, user experience, and scope
Phase 2: Planning
Once the user indicates they are ready to plan:
- Summarize all the requirements gathered from the Q&A session
- Use EnterPlanMode to transition into plan mode
- Explore the codebase to understand existing patterns and architecture
- Create a detailed implementation plan based on the gathered requirements
- Present the plan for user approval before implementation
Starting the Session
The user wants to plan: $ARGUMENTS
Begin Phase 1 now. Start by asking your first round of clarifying questions about this task.
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 · 45 lines · 11 tokens per session scan A ea8a6d13f447
collaborative-plan is a command published in the GitHub repository jimmc414/claude-code-plugin-marketplace (4 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 389 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-31.
Other commands, from other repositories
crash-report
Generate a crash report from Firebase Crashlytics for iOS and Android.
prep-pr
Prepare a PR for an upstream open source project with proper template compliance.
check-pr
Check a PR's CI status, reviews, comments, and merge readiness.
review
Review the current branch's changes for quality, bugs, and best practices.
speckit.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.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.