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 agentmods add skills/saadshahd/moo.md/clarifynpx skills add saadshahd/moo.md --skill clarifygit clone --depth 1 https://github.com/saadshahd/moo.mdWrote 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/saadshahd/moo.md/clarify)<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>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.00027 | $0.00391 |
| Opus 5 | $0.00014 | $0.00196 |
| Sonnet 5 | $0.00005 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
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.
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
- Name the readings apart — one line each, ending in what each would build or do differently.
- 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.
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 · 41 lines · 27 tokens per session scan A 2fa39067a9d7
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.
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.
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]…
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…
lark-openapi-explorer
飞书/Lark 原生 OpenAPI 探索:从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark- skill 或 lark-cli 已注册命令满足,需要查找并调用原生飞书 OpenAPI 时使用。.
lark-workflow-standup-report
日程待办摘要:编排 calendar +agenda 和 task +get-my-tasks,生成指定日期的日程与未完成任务摘要。适用于了解今天/明天/本周的安排。.
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…