Borrowing it
Nothing to install: this file belongs to aget-framework/aget. 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/aget-framework/aget/main/.claude/skills/aget-ask/SKILL.mdgit clone --depth 1 https://github.com/aget-framework/agetWrote 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/aget-framework/aget/aget-ask)<a href="https://agentmods.dev/skills/aget-framework/aget/aget-ask"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-ask/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/aget-framework/aget/aget-ask"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-ask.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00045 | $0.02131 |
| Opus 5.5 | $0.00018 | $0.00852 |
| Sonnet 5.5 | $0.00009 | $0.00426 |
| Haiku 4.5 | $0.00005 | $0.00213 |
Grade A, and why
aget-ask 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- aget-ask — 95% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aget-ask
Ask clarifying questions as a measurement instrument for next-action prediction. Default: --clarification.
Instructions
This skill formalizes asking clarifying questions as an entropy-reduction tool, not UX politeness. Quality is measured by pre/post confidence delta on the agent's top-1 interpretation of the principal's intent — not by thoroughness, count, or category coverage.
Clarification Mode (default: --clarification)
Generate 2-4 clarifying questions that maximally narrow the prediction distribution over what the principal wants next.
Execution:
-
Pre-ask measurement: Record the agent's top-1 interpretation of the principal's intent + confidence (0.0-1.0).
-
Entropy threshold check: If confidence ≥ 0.70, proceed with best-guess + verify instead of asking. If < 0.70, continue.
-
Generate candidates: Produce 4-8 candidate questions covering:
- Frame-choice (which model/framing applies)
- Replace-or-layer (affects which existing artifacts get modified)
- Scope boundary (what's in/out for this turn)
- Decision type (commitment level)
-
Filter decorative / context-answerable:
- Drop questions answerable from memory or KB context
- Drop wordsmithing between near-equivalent options
- Drop questions self-labeled "deferrable" in the draft
-
Rank by load-bearing weight: Estimate how much each question's answer would change the next action. Higher = ranked earlier.
-
Cap at 2-4: Top 2-4 questions only. If the problem genuinely needs 5+, the input had structural ambiguity — consider re-scoping the request instead of adding questions.
-
Order strictly by descending load-bearing weight, NOT by category altitude. If your draft contains phrases like "hiding at the bottom", "biggest shape-determining", or "flag for alignment" attached to a non-first question, reorder before presenting.
-
Present: Numbered questions with 2-3 concrete option examples per question to make answering cheap.
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 · 165 lines · 45 tokens per session scan A 3c9c65b4dd2c
aget-ask is a skill published in the GitHub repository aget-framework/aget (12 stars, last pushed 7d ago), licensed Apache-2.0. It adds 45 tokens to every session and 2,131 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
aget-close-project
Close a PROJECTPLAN with verifiable-assertion gate (V-tests + commits + retrospective), deferred-surface scan for next-plan handoff, and status transition (ACTIVE → COMPLETE / CLOSED / ABANDONED / SUPERSEDED). Strict counterpart to /aget-create-project (D71 Layer 2). Closes asymmetric verb-pair gap at PROJECTPLAN…
aget-release-critique
Adversarial review with the Critic perspective of the Release Delivery Triad (L818). Dual mandate — spec coverage audit plus deep bug finding, asking what breaks in the field and which assumptions are wrong. Superseded by /aget-check-release.
aget-release-audit-specs
Audit specifications with the Spec Auditor perspective of the Release Delivery Triad (L818) — coverage and consistency mode, asking whether a spec covers all behaviors and where gaps or contradictions remain. Superseded by /aget-check-release.
aget-release-build
Execute release gate deliverables with the Builder perspective of the Release Delivery Triad (L818) — speed-optimized execution asking whether the work is done, fast, and functional. Superseded by /aget-create-release.
aget-file-issue
File issues with L520 governance compliance.
aget-propose-actions
Propose ranked next-best actions with evidence grounding, time budgets, and execute-all default. Formalizes the fleet's highest-frequency interaction pattern.