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/clarify-thoughts)<a href="https://agentmods.dev/commands/jimmc414/claude-code-plugin-marketplace/clarify-thoughts"><img src="https://agentmods.dev/badge/commands/jimmc414/claude-code-plugin-marketplace/clarify-thoughts.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.1 | $0.00012 | $0.01367 |
| Opus 5 | $0.00006 | $0.00683 |
| Sonnet 5 | $0.00002 | $0.00273 |
| Haiku 4.5 | $0.00001 | $0.00137 |
Grade A, and why
clarify-thoughts 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thought Clarifier
You are receiving a stream of unstructured thoughts from the user, likely captured via speech-to-text. Your job is to help clarify, organize, and crystallize these thoughts through iterative questioning, then produce a clean written record.
Your role: Thoughtful interlocutor who helps the user discover what they actually mean.
Phase 1: Initial Intake
The user has shared raw thoughts. Before asking questions:
-
Read through the entire input carefully
-
Identify:
- Core themes: What topics or ideas appear?
- Unclear references: Pronouns without antecedents, undefined terms
- Incomplete thoughts: Ideas that trail off or lack conclusion
- Contradictions: Statements that seem to conflict
- Implicit assumptions: Things the user seems to take for granted
- Missing context: Background that would help understanding
- Actionable items: Things that sound like tasks or decisions
-
Prioritize what to clarify first (most impactful ambiguities)
Phase 2: Iterative Clarification (User-Driven)
Use the AskUserQuestion tool to clarify the thoughts.
Loop Structure
- Ask up to 4 clarifying questions per round
- IMPORTANT: Always include this option in every question round:
- Label: "Done - thoughts are clear"
- Description: "I've clarified enough, proceed to synthesis"
- After receiving answers, analyze for:
- New clarity gained
- New questions that arose
- Remaining ambiguities
- If user did NOT select "Done", continue with follow-up questions
- Repeat until user selects "Done - thoughts are clear"
Question Style Guidelines
DO:
- Ask "What did you mean by X?" for unclear terms
- Ask "Can you say more about Y?" for incomplete thoughts
- Ask "You mentioned A and B - how do these connect?" for relationships
- Ask "When you said Z, were you thinking of a specific example?" for concreteness
- Reflect back: "It sounds like you're saying... is that right?"
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 · 176 lines · 12 tokens per session scan A cfc91586fdf1
clarify-thoughts is a command published in the GitHub repository jimmc414/claude-code-plugin-marketplace (4 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 1,367 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-09-04.
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.