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/adriannoes/awesome-agentic-aiWrote 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/adriannoes/awesome-agentic-ai/clarify-task)<a href="https://agentmods.dev/commands/adriannoes/awesome-agentic-ai/clarify-task"><img src="https://agentmods.dev/badge/commands/adriannoes/awesome-agentic-ai/clarify-task.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.00000 | $0.00236 |
| Opus 5 | $0.00000 | $0.00118 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
clarify-task 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 8d 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.
What it actually says
Clarify Task
Overview
Break down ambiguous tasks into clear, actionable steps before implementation.
Steps
-
Identify ambiguity
- What is unclear or underspecified?
- What assumptions might we be making?
- What could go wrong if we guess wrong?
-
Ask clarifying questions
- One question at a time
- Prefer multiple choice when possible
- Focus on: purpose, constraints, success criteria
-
Present interpretations
- If multiple interpretations exist, list them
- Don't pick silently — surface tradeoffs
- Get explicit confirmation before proceeding
-
Define acceptance criteria
- What does "done" look like?
- How will we verify success?
- What are the boundaries of scope?
-
Produce actionable steps
- Ordered list of concrete steps
- Each step has a clear verification
- Share with user for approval before implementation
Output
Deliver a brief task breakdown with:
- Clarified scope and constraints
- Explicit assumptions (or questions still open)
- Ordered steps with verification criteria
- User sign-off before coding
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.
- 8d ago First seen · 41 lines · 0 tokens per session scan A 83c69468f265
clarify-task is a command published in the GitHub repository adriannoes/awesome-agentic-ai (56 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 236 tokens. 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
design-onboarding
Design a first-run experience end to end — activation path, progressive disclosure, and time to first value.
assistant-auto
Orchestrator in automatic mode. Choose the workflow that semantically fits based on the request + the injected repo context, then execute immediately via Skill.
growth-email
Create transactional and marketing email templates.
amby.clarify
Resolve the open [NEEDS CLARIFICATION] markers in a feature spec.
aw-upgrade
Upgrade gh-aw extension, recompile and validate all workflows, and open a PR with changes.
review
Conduct a five-axis code review — correctness, readability, architecture, security, performance.