clarify

clarify is a skill for Claude Code from saadshahd/moo.md. It costs 27 tokens per session (391 once invoked), scanned A, original, MIT.

A clarification guide for requests that could reasonably mean two different things. It helps confirm which interpretation the user wants before work begins.

In plain words
What is it for?
It is for identifying competing interpretations, explaining how they differ, and asking the user to choose once.
Why use it?
It prevents building the wrong result when the same words could lead to different implementations.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the hope plugin — 20 skills, 1 command, 3 hooks shipped together

Install

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.

agentmods
npx agentmods add skills/saadshahd/moo.md/clarify
Any agent
npx skills add saadshahd/moo.md --skill clarify
Clone the repo
git clone --depth 1 https://github.com/saadshahd/moo.md

Made for: Claude Code.

Or install hope, the plugin that ships this one along with the rest of its 20 skills, 1 command, 3 hooks.

Wrote 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.

agentmods badge for clarify

README.md
[![agentmods](https://agentmods.dev/badge/skills/saadshahd/moo.md/clarify.svg)](https://agentmods.dev/skills/saadshahd/moo.md/clarify)
Your own site
<a href="https://agentmods.dev/skills/saadshahd/moo.md/clarify"><img src="https://agentmods.dev/badge/skills/saadshahd/moo.md/clarify.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 391 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.00391
Opus 5 $0.00014 $0.00196
Sonnet 5 $0.00005 $0.00078
Haiku 4.5 $0.00003 $0.00039

Measured 6d ago against content hash 2fa39067a9d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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 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.

hope/skills/clarify/SKILL.md · 41 lines

What it actually says

Extract

From the user's words or the conversation:

  • The ask as given in the context
  • Its readings — the two (or more) ways the words could be taken.

Gate

Proceed only when: the readings would build or do different things.

Anything else, say which in one plain line — never clarify anyway:

  • Every reading leads to the same work → skip the pick and proceed with the work. Never stage a choice that changes nothing.
  • The ask is already concrete and the pull is to keep questioning it — that is challenging its decisions, not picking a reading → use interrogate skill.
  • The user holds something they can't yet put into words — no reading of the words captures it → use elicit skill.

Stage

  1. Name the readings apart — one line each, ending in what each would build or do differently.
  2. Ask the user to pick.

One exchange: readings out, pick back. Never ask a second question. If the user cannot pick, the words are not the problem — stop clarifying; use elicit skill.

Output

Take the pick as the confirmed ask. Restate it in one line.

The pick resolved the words — now check whether the restated ask is clear enough to return to the work it interrupted: would anything still unresolved change what gets built?

  • Nothing would → proceed with the work.
  • Something would, and the user holds it but hasn't said it → use elicit skill.
  • Something would, and it's a decision inside the ask that needs defending → use interrogate skill.

Clarify's one exchange is spent — any further question runs under the named skill's procedure, never as another round of clarifying.

Changes

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.

  1. 6d ago First seen · 41 lines · 27 tokens per session scan A 2fa39067a9d7

Subscribe to this mod's changes

clarify is a skill published in the GitHub repository saadshahd/moo.md (34 stars, last pushed 20d ago), licensed MIT. It adds 27 tokens to every session and 391 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-08-30.

Related

Other skills, from other repositories

session-recap

Document Claude Code sessions by extracting knowledge into cross-referenced documentation. Triggers on "recap the session", "summarize the work", or after significant code changes.

sxhmilyoyo/sundayhao-plugins · 39 tokens

knowledge-bank-lookup

Delegates knowledge bank lookups to Explore subagents with reflections-first strategy that learns from past mistakes. Checks /reflections/ directory before documentation to extract documented failures to avoid and proven approaches to apply. Automatically triggers when user mentions services ([project-a], [project-b]…

sxhmilyoyo/sundayhao-plugins · 94 tokens

kb-ingest

Ingest external sources into the knowledge bank through interactive study or quick filing. Two modes — Quick (summarize → file) and Study (theme-by-theme deep dive with online research and personal notes → multi-layer KB output → optional blog/slack synthesis). Triggers on "ingest this", "study this article", "add to…

sxhmilyoyo/sundayhao-plugins · 152 tokens

lark-openapi-explorer

飞书/Lark 原生 OpenAPI 探索:从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark- skill 或 lark-cli 已注册命令满足,需要查找并调用原生飞书 OpenAPI 时使用。.

DropFan/claude-code-plugins · 76 tokens

lark-workflow-standup-report

日程待办摘要:编排 calendar +agenda 和 task +get-my-tasks,生成指定日期的日程与未完成任务摘要。适用于了解今天/明天/本周的安排。.

DropFan/claude-code-plugins · 53 tokens

session-manager

Manage current Claude Code session metadata — set project, tags, and summary on session.md via Obsidian CLI. Use this skill whenever the user wants to tag, categorize, name, label, summarize, or organize the current session. Triggers on phrases like "tag this session", "this was about X", "mark this as", "session…

sxhmilyoyo/sundayhao-plugins · 132 tokens