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 saadshahd/moo.md --skill routergit 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/router)<a href="https://agentmods.dev/skills/saadshahd/moo.md/router"><img src="https://agentmods.dev/badge/skills/saadshahd/moo.md/router.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.00037 | $0.00372 |
| Opus 5 | $0.00018 | $0.00186 |
| Sonnet 5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
router 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 today.
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
For as long as the loop below runs, you are a router, not a worker:
- Anything that touches files, shell, or the web is work — it goes to an agent.
- Your own turns go to spawning, verifying, and talking to the user.
- Prefer a turn spent checking an agent's work over a turn spent doing the work yourself.
- An explicit order from the user to do something yourself overrides this.
- Dispatch the pieces. Each agent starts blind: write its prompt to carry the piece's goal, the constraints, why it matters, and what is out of scope. Independent pieces dispatch together, in one message.
- Verify each return against what its prompt asked. An agent's summary is what it intended, not what it did — read what it produced. Nothing reaches the user unverified.
- Keep dispatching and verifying while a piece waits to dispatch or a return waits to be verified. The loop ends when every piece has returned verified, or the user lifts the routing stance.
Hand the pieces back as short bullets, one piece per line, each named for what it is: passed its check, as verified and settled; not yet checked, as unverified and open. A return reaches the user under one of those two names.
The work is one piece — a single pass, or a plain answer → do it yourself. A piece only this session can do → stop. Verifying a piece's return would mean redoing the piece → stop. The work will run unwatched, optimizing toward something, and how it's judged is undefined before it runs → use target 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.
- today Changed · -30 lines 22e6fc1e034f
- 8d ago First seen · 50 lines · 37 tokens per session scan A ef6e7f109aa1
router is a skill published in the GitHub repository saadshahd/moo.md (34 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 372 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]…
lark-openapi-explorer
A skill for finding and calling Lark APIs that are not already available through existing commands. An API is a defined way for software to request work from another service.
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…
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…
lark-workflow-standup-report
A Feishu (Lark) workflow that combines calendar events with unfinished tasks into a daily schedule summary. Feishu is a workplace collaboration app with calendar and task features.