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/explainnpx skills add saadshahd/moo.md --skill explaingit 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/explain)<a href="https://agentmods.dev/skills/saadshahd/moo.md/explain"><img src="https://agentmods.dev/badge/skills/saadshahd/moo.md/explain.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 | $0.00025 | $0.00642 |
| Opus 5 | $0.00013 | $0.00321 |
| Sonnet 5 | $0.00005 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
explain 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 5d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extract
From the conversation/context/user:
- The thing — the settled design, term, behavior, or number to put across.
- The evidence it's missing — where the user said or showed they don't hold it.
Gate
Proceed only when: the thing is settled and the user has said or shown they don't hold it.
Anything else, say which in one plain line — never explain anyway:
- The thing is not settled — still being weighed, designed, or decided → there is nothing settled to explain yet.
- The user already holds it → there is nothing missing to put across.
- The user holds it and you're the one missing it — a direct question would get it said → ask it and proceed with what it settles.
- The user holds it but cannot yet put it into words → use elicit skill.
- The user wants a verdict on it, not an understanding of it → use judge skill.
Retrieve
Never explain from a guess. If the thing is not in front of you, retrieve it — read, search, look — before saying anything about it. Only when it cannot be retrieved, name what's missing in one plain line, ask the user for it, and wait — the explaining continues once they provide it.
State
State the thing in one plain line — no jargon, no preamble, no build-up. Stop there: never push the full picture unpulled. Name the two or three directions the user could pull next, and wait.
Answer
The user drives the loop: each iteration is one pull from them — a follow-up question, a "tell me more", an "I still don't get X".
- Answer each pull with one plain line first, depth only where pulled.
- "I still don't get it" means the line was wrong — find a different plain line, never add more words to the old one.
- After each line, wait for the next pull.
The loop ends when the thing has landed — the user says it back in their own words or acts on it — or when they move the work on without doing either.
Output
The landed thing is the result — it lives in the user's head, not in anything handed back. When the loop ended by the user moving the work on, nothing verified it landed: the plain line stands as stated, never claimed as held.
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.
- 5d ago First seen · 56 lines · 25 tokens per session scan A fed99ff6c663
explain is a skill published in the GitHub repository saadshahd/moo.md (34 stars, last pushed 19d ago), licensed MIT. It adds 25 tokens to every session and 642 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…