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 skills add flanliulf/SpecLite --skill bmad-advanced-elicitationgit clone --depth 1 https://github.com/flanliulf/SpecLiteWrote 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/skills/flanliulf/speclite/bmad-advanced-elicitation)<a href="https://agentmods.dev/skills/flanliulf/speclite/bmad-advanced-elicitation"><img src="https://agentmods.dev/badge/skills/flanliulf/speclite/bmad-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/skills/flanliulf/speclite/bmad-advanced-elicitation"><img src="https://agentmods.dev/badge/skills/flanliulf/speclite/bmad-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.00056 | $0.01396 |
| Opus 5.5 | $0.00022 | $0.00558 |
| Sonnet 5.5 | $0.00011 | $0.00279 |
| Haiku 4.5 | $0.00006 | $0.00140 |
Grade A, and why
bmad-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 1mo 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
100% identical to bmad-advanced-elicitation — 129 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Advanced Elicitation
Goal: Push the LLM to reconsider, refine, and improve its recent output.
CRITICAL LLM INSTRUCTIONS
- MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER
- DO NOT skip steps or change the sequence
- HALT immediately when halt-conditions are met
- Each action within a step is a REQUIRED action to complete that step
- Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the
communication_language
INTEGRATION (When Invoked Indirectly)
When invoked from another prompt or process:
- Receive or review the current section content that was just generated
- Apply elicitation methods iteratively to enhance that specific content
- Return the enhanced version back when user selects 'x' to proceed and return back
- The enhanced content replaces the original section content in the output document
FLOW
Step 1: Method Registry Loading
Action: Load ./methods.csv for elicitation methods. If party-mode may participate, resolve the agent roster via:
python3 {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} --key agents
The resolver merges four layers in order: _bmad/config.toml (installer base, team-scoped), _bmad/config.user.toml (installer base, user-scoped), _bmad/custom/config.toml (team overrides), and _bmad/custom/config.user.toml (personal overrides). Each entry under agents is keyed by the agent's code and carries name, title, icon, description, module, and team.
CSV Structure
- category: Method grouping (core, structural, risk, etc.)
- method_name: Display name for the method
- description: Rich explanation of what the method does, when to use it, and why it's valuable
- output_pattern: Flexible flow guide using arrows (e.g., "analysis -> insights -> action")
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 143 lines · 56 tokens per session scan A 705cc827cab8
bmad-advanced-elicitation is a skill published in the GitHub repository flanliulf/SpecLite (4 stars, last pushed 4d ago), licensed MIT. It adds 56 tokens to every session and 1,396 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to bmad-advanced-elicitation, differing in 129 lines, and is treated as a copy.
Other skills, from other repositories
build-knowledge-base
Build or update a persistent repo knowledge base graph.
implement
Execute an approved phase plan with TDD, dependency-aware task fan-out, required evidence, and a strict iteration handoff.
research-codebase
Document codebase as-is through comprehensive research.
review-comments
Execute a feature-level review-comments cycle — aggregate unaddressed PR comments across every Feature.Repos PR, address or dismiss each one, and emit the standard handoff.
inquire
Transform feature requests into research questions.
validate-phase-plan-scope
Per-phase plan scope validation gate - ensures the plan maps the approved roadmap phase into tasks without silent drift.