Borrowing it
Nothing to install: this file belongs to hollandkevint/thinkhaven. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hollandkevint/thinkhaven/main/.claude/commands/BMad/tasks/advanced-elicitation.mdgit clone --depth 1 https://github.com/hollandkevint/thinkhavenWrote 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/hollandkevint/thinkhaven/advanced-elicitation)<a href="https://agentmods.dev/commands/hollandkevint/thinkhaven/advanced-elicitation"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/advanced-elicitation/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/hollandkevint/thinkhaven/advanced-elicitation"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/advanced-elicitation.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.00000 | $0.01010 |
| Opus 5 | $0.00000 | $0.00505 |
| Sonnet 5 | $0.00000 | $0.00202 |
| Haiku 4.5 | $0.00000 | $0.00101 |
Grade A, and why
advanced-elicitation 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 9d 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.
This is a copy
97% identical to advanced-elicitation — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/advanced-elicitation Task
When this command is used, execute the following task:
Advanced Elicitation Task
Purpose
- Provide optional reflective and brainstorming actions to enhance content quality
- Enable deeper exploration of ideas through structured elicitation techniques
- Support iterative refinement through multiple analytical perspectives
- Usable during template-driven document creation or any chat conversation
Usage Scenarios
Scenario 1: Template Document Creation
After outputting a section during document creation:
- Section Review: Ask user to review the drafted section
- Offer Elicitation: Present 9 carefully selected elicitation methods
- Simple Selection: User types a number (0-8) to engage method, or 9 to proceed
- Execute & Loop: Apply selected method, then re-offer choices until user proceeds
Scenario 2: General Chat Elicitation
User can request advanced elicitation on any agent output:
- User says "do advanced elicitation" or similar
- Agent selects 9 relevant methods for the context
- Same simple 0-9 selection process
Task Instructions
1. Intelligent Method Selection
Context Analysis: Before presenting options, analyze:
- Content Type: Technical specs, user stories, architecture, requirements, etc.
- Complexity Level: Simple, moderate, or complex content
- Stakeholder Needs: Who will use this information
- Risk Level: High-impact decisions vs routine items
- Creative Potential: Opportunities for innovation or alternatives
Method Selection Strategy:
-
Always Include Core Methods (choose 3-4):
- Expand or Contract for Audience
- Critique and Refine
- Identify Potential Risks
- Assess Alignment with Goals
-
Context-Specific Methods (choose 4-5):
- Technical Content: Tree of Thoughts, ReWOO, Meta-Prompting
- User-Facing Content: Agile Team Perspective, Stakeholder Roundtable
- Creative Content: Innovation Tournament, Escape Room Challenge
- Strategic Content: Red Team vs Blue Team, Hindsight Reflection
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.
- 9d ago First seen · 124 lines · 0 tokens per session scan A b4130130432a
advanced-elicitation is a command published in the GitHub repository hollandkevint/thinkhaven (5 stars, last pushed 10d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,010 tokens. A static security scan graded it A with 0 findings. It is 97% identical to advanced-elicitation, differing in 2 lines, and is treated as a copy.
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.