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 dork-labs/dorkos --skill clarifying-requirementsgit clone --depth 1 https://github.com/dork-labs/dorkosWrote 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/dork-labs/dorkos/clarifying-requirements)<a href="https://agentmods.dev/skills/dork-labs/dorkos/clarifying-requirements"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/clarifying-requirements/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/dork-labs/dorkos/clarifying-requirements"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/clarifying-requirements.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.01389 |
| Opus 5 | $0.00023 | $0.00694 |
| Sonnet 5 | $0.00009 | $0.00278 |
| Haiku 4.5 | $0.00005 | $0.00139 |
Grade A, and why
clarifying-requirements 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clarifying Requirements
Analyze user prompts for gaps, ambiguities, and unstated assumptions — then ask the questions the user failed to ask BEFORE beginning work.
Core Principle
Don't just answer what was asked — anticipate what SHOULD have been asked. Users often don't know what they don't know. Surface gaps in their thinking, unstated assumptions that could derail implementation, and scope ambiguities that lead to rework. The one test that matters: "Can I implement this without making assumptions?" If not, ask about the assumptions you'd have to make.
When to Apply
Activate proactive clarification when the request shows:
| Signal | Example | Why It Matters |
|---|---|---|
| Vague action verbs | "add", "improve", "fix" without specifics | Undefined scope leads to wrong implementation |
| Missing constraints | "make it faster" without metrics | No way to know when you're done |
| Complexity underestimation | "just add a button", "simple form", "quick" | Often hides error/loading/permission states |
| Multiple features bundled | "add X and Y and also Z" | Scope creep, unclear priority |
| Goal without criteria | "users should be able to..." | No acceptance criteria |
| Assumed context | "fix the bug" (which bug?), "like the other one" | Missing reproduction steps / referent |
Questioning Strategy
Do:
- Limit to 2-4 questions — pick the highest-impact clarifications
- Explain why each question matters ("This affects routing, state management, and URL structure")
- Group related questions by theme (scope vs technical decisions)
- Use AskUserQuestion for bounded choices — see Recommendation Discipline below
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.
- 6d ago First seen · 141 lines · 45 tokens per session scan A 2f4feb5f58a6
clarifying-requirements is a skill published in the GitHub repository dork-labs/dorkos (9 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 1,389 once invoked, about $0.0002 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-03.
Other skills, from other repositories
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
hive.pdf
Read, write, merge, split, rotate, watermark, encrypt, and OCR PDF files using Python (pypdf, pdfplumber, reportlab, pypdfium2) and command-line tools (poppler-utils, qpdf). Use when the user asks to extract text/tables/images from a PDF, create or modify a PDF, combine or split PDFs, OCR a scanned PDF…
hive.note-taking
Maintain a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need.
sdlc-accelerate
End-to-end SDLC ramp-up from idea to construction-ready with automated phase transitions.
ralph-memory
Manage Al semantic memory entries — list, query, and clear lessons learned across loop iterations.
project-awareness
Detect project type, AIWG framework state, team configuration, and active work to summarize status and recommend next actions.