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 owainlewis/agent-skills --skill clarifygit clone --depth 1 https://github.com/owainlewis/agent-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/owainlewis/agent-skills/clarify)<a href="https://agentmods.dev/skills/owainlewis/agent-skills/clarify"><img src="https://agentmods.dev/badge/skills/owainlewis/agent-skills/clarify.svg" alt="Measured on agentmods" 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.00070 | $0.00625 |
| Opus 5 | $0.00035 | $0.00313 |
| Sonnet 5 | $0.00014 | $0.00125 |
| Haiku 4.5 | $0.00007 | $0.00063 |
Grade A, and why
clarify 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clarify
Turn a rough request into a prompt another agent can execute.
Choose a mode
- Refine directly when the goal is clear and missing details have safe defaults.
- Interview when one unresolved choice would materially change behaviour, data, security, compatibility, cost, output, or proof.
- Execute the clarified prompt only when the user explicitly asks to run it or says "just do it."
Process
- Read the request and any referenced material.
- For repository work, inspect discoverable context such as
AGENTS.md,CLAUDE.md,README.md, the file tree, and relevant code before asking questions. - Extract the goal, current state, inputs, outputs, constraints, scope boundaries, failure behaviour, and success checks.
- Resolve unambiguous references and project conventions from the available context.
- Use a sensible assumption when the user can change it later without reworking the task.
- Ask one question when no safe assumption exists. After the answer, check whether another important decision remains.
- Include all context needed to execute the prompt. Do not refer to "our discussion" or information outside the prompt.
Ask useful questions
Ask about decisions such as:
- which input, file, directory, system, or audience is in scope
- what output must exist, where it belongs, and whether it may overwrite anything
- required behaviour for bad input, missing data, network failure, or partial success
- tradeoffs that change product behaviour, security, compatibility, cost, or architecture
- the observable result or check that proves completion
Do not ask about cosmetic choices, conventions the repository answers, details already supplied, or preferences with an obvious low-risk default.
Use this shape:
Question: <one decision>
Recommendation: <answer> because <short reason>.
Write the final prompt
Include only what changes execution:
- goal
- relevant context and current state
- exact inputs and outputs
- in-scope and out-of-scope work
- constraints and safe assumptions
- required failure behaviour
- success criteria and verification
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 71 lines · 70 tokens per session scan A 956be554cf38
clarify is a skill published in the GitHub repository owainlewis/agent-skills (44 stars, last pushed 17d ago), licensed MIT. It adds 70 tokens to every session and 625 once invoked, about $0.0003 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
x-tweet-by-conversation
Collects every tweet in an X (Twitter) conversation thread given a conversation id (root tweet id) — the focal tweet plus all replies, sub-replies, and quote chains — and returns normalized per-tweet data with text, author, engagement counts, media, hashtags, mentions, inreplyto mapping, and cursor for pagination. Use…
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
auditing-azure-active-directory-configuration
Auditing Microsoft Entra ID (Azure Active Directory) configuration to identify risky authentication policies, overly permissive role assignments, stale accounts, conditional access gaps, and guest user risks using AzureAD PowerShell, Microsoft Graph API, and ScoutSuite.
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.