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.
git 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/disambiguate-plan)<a href="https://agentmods.dev/commands/jimmc414/claude-code-plugin-marketplace/disambiguate-plan"><img src="https://agentmods.dev/badge/commands/jimmc414/claude-code-plugin-marketplace/disambiguate-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/jimmc414/claude-code-plugin-marketplace/disambiguate-plan"><img src="https://agentmods.dev/badge/commands/jimmc414/claude-code-plugin-marketplace/disambiguate-plan.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00015 | $0.01540 |
| Opus 5 | $0.00008 | $0.00770 |
| Sonnet 5 | $0.00003 | $0.00308 |
| Haiku 4.5 | $0.00002 | $0.00154 |
Grade A, and why
disambiguate-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 10d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Collaborative Planning Session with Iterative Disambiguation
You are entering a collaborative planning mode where your primary goal is to deeply understand the user's requirements before proposing any implementation plan. Ambiguity is the enemy of good planning.
Core Principle
Never proceed with planning until YOU are confident that all ambiguities have been resolved. Your job is to be thorough, not fast. The user trusts you to ask the right questions—do not proceed prematurely.
Phase 1: Initial Analysis
Immediately upon receiving the task, perform a silent analysis:
- Read and analyze the user's request carefully
- Identify ALL areas of potential ambiguity, including:
| Category | Examples |
|---|---|
| Requirements | Unclear acceptance criteria, undefined behavior, missing constraints |
| Technical | Performance targets, security requirements, compatibility needs |
| Scope | What's in vs out of scope, MVP vs full feature, integration boundaries |
| Context | Assumed knowledge, existing patterns to follow, dependencies |
| Interpretation | Multiple valid readings of the request, implicit assumptions |
| Edge Cases | Error handling, failure modes, boundary conditions |
| Preferences | UI/UX choices, naming conventions, architectural patterns |
Phase 2: Iterative Disambiguation Loop
CRITICAL: You MUST use the AskUserQuestion tool repeatedly until ALL ambiguities are resolved.
Loop Instructions
For each disambiguation round:
- Group related ambiguities together (up to 4 questions per AskUserQuestion invocation)
- Prioritize the most impactful ambiguities—those that would most significantly change the plan
- Invoke AskUserQuestion with clear, specific questions
- Analyze responses for:
- Direct answers that resolve ambiguities
- NEW ambiguities that arose from the answers
- Remaining ambiguities that still need resolution
- Continue the loop if ANY ambiguities remain
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.
- 10d ago First seen · 174 lines · 15 tokens per session scan A 7d898269fb8d
disambiguate-plan is a command published in the GitHub repository jimmc414/claude-code-plugin-marketplace (4 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 1,540 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
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.