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/intentnpx skills add saadshahd/moo.md --skill intentgit 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/intent)<a href="https://agentmods.dev/skills/saadshahd/moo.md/intent"><img src="https://agentmods.dev/badge/skills/saadshahd/moo.md/intent.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.00031 | $0.00504 |
| Opus 5 | $0.00015 | $0.00252 |
| Sonnet 5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
intent 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extract
From the conversation/context/user:
- The ask as given — the words on the table.
- What blocks it — everything that would have to be invented to start the work now.
Gate
Proceed only when: starting the work now would mean inventing what the user means.
Anything else, say which in one plain line — never work the ask over anyway:
- The ask is already one confirmed thing → proceed with the work.
- The WHAT is confirmed and the open question is the technical path — architecture, technology, design → use shape skill.
Route
Before routing anything: retrieve what the record, the repo, or the world can answer. Only what the user alone holds routes to a skill.
Route each blocker by what it is, invoking the named skill with the Skill tool:
- The words admit two readings that would build different things → use clarify skill.
- The user holds what they want but can't yet say it → use elicit skill.
- The user is missing something already settled — what exists, what a thing means — and can't ask past it → use explain skill.
- The ask arrives already committed — a locked proposal with undefended decisions inside → use interrogate skill.
What each skill gives back re-enters the routing: a clarify pick can surface something the user can't express; an elicit record can leave words with two readings; an explain can let the user finally say the ask; an interrogate answer can amend the ask. Route again until nothing blocks the ask.
Where the input leaves it open, ask the negative once — what should this NOT do — before closing.
Output
The work order is the result: the ask restated in one line, confirmed by the user — plus what it must NOT do, where that surfaced. The routing ends only when starting the work would invent nothing.
Then check what still stands open:
- Nothing — or one way to build it is already plain → proceed with the work.
- The WHAT is confirmed but more than one way to build it remains → use shape skill.
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 · 47 lines · 31 tokens per session scan A 363f5b7e0f90
intent is a skill published in the GitHub repository saadshahd/moo.md (34 stars, last pushed 18d ago), licensed MIT. It adds 31 tokens to every session and 504 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-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…