AAS Core is a local control plane for coding agents that lets them search a large catalogue of skills, choose a stack, validate it, and create a reproducible plan. It is used to assemble and review agent workflows through its CLI, local MCP server, catalogue, plugins, and Workbench. The catalogue add-ons provide the skills, plugins, bundles, and workflows that AAS Core helps agents select and validate.
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 sickn33/agentic-awesome-skills --skill ask-questions-if-underspecifiedgit clone --depth 1 https://github.com/sickn33/agentic-awesome-skillsWrote 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/sickn33/agentic-awesome-skills/ask-questions-if-underspecified)<a href="https://agentmods.dev/skills/sickn33/agentic-awesome-skills/ask-questions-if-underspecified"><img src="https://agentmods.dev/badge/skills/sickn33/agentic-awesome-skills/ask-questions-if-underspecified/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/sickn33/agentic-awesome-skills/ask-questions-if-underspecified"><img src="https://agentmods.dev/badge/skills/sickn33/agentic-awesome-skills/ask-questions-if-underspecified.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.00020 | $0.00957 |
| Opus 5 | $0.00010 | $0.00478 |
| Sonnet 5 | $0.00004 | $0.00191 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
ask-questions-if-underspecified 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
8 near-identical copies found in the catalogue:
- ask-questions-if-underspecified — 100% identical, 1 lines differ
- ask-questions-if-underspecified — 100% identical, 1 lines differ
- ask-questions-if-underspecified — 98% identical, 3 lines differ
- ask-questions-if-underspecified — 98% identical, 3 lines differ
- ask-questions-if-underspecified — 98% identical, 3 lines differ
- ask-questions-if-underspecified — 98% identical, 3 lines differ
- ask-questions-if-underspecified — 94% identical, 8 lines differ
- ask-questions-if-underspecified — 94% identical, 9 lines differ
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ask Questions If Underspecified
When to Use
Use this skill when a request has multiple plausible interpretations or key details (objective, scope, constraints, environment, or safety) are unclear.
When NOT to Use
Do not use this skill when the request is already clear, or when a quick, low-risk discovery read can answer the missing details.
Goal
Ask the minimum set of clarifying questions needed to avoid wrong work; do not start implementing until the must-have questions are answered (or the user explicitly approves proceeding with stated assumptions).
Workflow
1) Decide whether the request is underspecified
Treat a request as underspecified if after exploring how to perform the work, some or all of the following are not clear:
- Define the objective (what should change vs stay the same)
- Define "done" (acceptance criteria, examples, edge cases)
- Define scope (which files/components/users are in/out)
- Define constraints (compatibility, performance, style, deps, time)
- Identify environment (language/runtime versions, OS, build/test runner)
- Clarify safety/reversibility (data migration, rollout/rollback, risk)
If multiple plausible interpretations exist, assume it is underspecified.
2) Ask must-have questions first (keep it small)
Ask 1-5 questions in the first pass. Prefer questions that eliminate whole branches of work.
Make questions easy to answer:
- Optimize for scannability (short, numbered questions; avoid paragraphs)
- Offer multiple-choice options when possible
- Suggest reasonable defaults when appropriate (mark them clearly as the default/recommended choice; bold the recommended choice in the list, or if you present options in a code block, put a bold "Recommended" line immediately above the block and also tag defaults inside the block)
- Include a fast-path response (e.g., reply
defaultsto accept all recommended/default choices) - Include a low-friction "not sure" option when helpful (e.g., "Not sure - use default")
- Separate "Need to know" from "Nice to know" if that reduces friction
- Structure options so the user can respond with compact decisions (e.g.,
1b 2a 3c); restate the chosen options in plain language to confirm
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 Changed · +1 lines d13ef519ce7b
- 6d ago First seen · 92 lines · 20 tokens per session scan A 38476277b736
ask-questions-if-underspecified is a skill published in the GitHub repository sickn33/agentic-awesome-skills (46,230 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 957 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-05.
Other skills, from other repositories
cli-builder
Professional CLI Builder skill. Improve code delivery speed and developer workflows through automation and modern tooling.
developer-portal
Professional Developer Portal Expert skill. Improve code delivery speed and developer workflows through automation and modern tooling.
dx-auditor
Professional Dx Auditor skill. Build performant, secure, and scalable backend logic and RESTful or GraphQL APIs.
formatter-setup
Professional Formatter Setup Expert skill. Improve code delivery speed and developer workflows through automation and modern tooling.
linting-configurator
Professional Linting Configurator Expert skill. Improve code delivery speed and developer workflows through automation and modern tooling.
readme-master
Professional Readme Master skill. Improve code delivery speed and developer workflows through automation and modern tooling.