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/terryso/autoqa-agent/advanced-elicitationgit clone --depth 1 https://github.com/terryso/AutoQA-AgentWrote 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/terryso/autoqa-agent/advanced-elicitation)<a href="https://agentmods.dev/commands/terryso/autoqa-agent/advanced-elicitation"><img src="https://agentmods.dev/badge/commands/terryso/autoqa-agent/advanced-elicitation.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.00004 | $0.00046 |
| Opus 5 | $0.00002 | $0.00023 |
| Sonnet 5 | $0.00001 | $0.00009 |
| Haiku 4.5 | $0.00000 | $0.00005 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- advanced-elicitation — 100% identical, 2 lines differ
What it actually says
Advanced Elicitation
LOAD and execute the task at: _bmad/core/tasks/advanced-elicitation.xml
Follow all instructions in the task file exactly as written.
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 · 10 lines · 4 tokens per session scan A 07844dbe41e5
advanced-elicitation is a command published in the GitHub repository terryso/AutoQA-Agent (134 stars, last pushed 7mo ago), licensed MIT. It adds 4 tokens to every session and 46 once invoked, about $0.0000 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-30.
Other commands, from other repositories
index
Complete reference for all 20 BMAD Planning & Orchestrator skills. Invoked as /bmad-planning-orchestrator: or auto-triggered by Claude. Includes migration map from old slash commands.
boss:ship
只跑部署环节：DevOps 构建部署 + 上线前门禁 + 部署报告。对已通过测试的项目单独可用，产出 deploy-report.md，门禁不可绕过。.
getting-started
Interactive 10-minute guided tour for new Claude Craft users.
from-spec
Extract Architecture Decision Records from a completed spec.
release
You are now acting as a Release Engineer. Automatically generate a changelog from git history to assist with version releases.
types
Debug and fix TypeScript type errors with systematic analysis and expert guidance.