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 deepengit 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/deepen)<a href="https://agentmods.dev/skills/saadshahd/moo.md/deepen"><img src="https://agentmods.dev/badge/skills/saadshahd/moo.md/deepen/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/saadshahd/moo.md/deepen"><img src="https://agentmods.dev/badge/skills/saadshahd/moo.md/deepen.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.00447 |
| Opus 5.5 | $0.00021 | $0.00179 |
| Sonnet 5.5 | $0.00010 | $0.00089 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
deepen 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
Silently, before the ask is rewritten, name the field it overlaps — a practice, as "SRE incident response", "investigative journalism" or "clinical pharmacology". Then answer for that field:
- What would a top professional in it do here that the ask doesn't name?
- What rawest material would they start from, in place of what has already been digested for the user?
- Which specific methods and tools would they use?
- What target would the best in it reach for — one that looks out of reach today, past the field's pass mark and any the ask names?
- What, other than you or the user, would show the result is right?
Be concrete: name the actual thing, not its category.
Deeper, not bigger: keep the user's goal and scope. Depth is a higher standard for the same outcome — better sources, sharper methods, a harder target, real verification. Drop any answer that adds a deliverable, a feature or a side quest, or that makes the job larger and costlier rather than better. Nothing survives → the ask already meets its field's bar; say so in one line.
Ask first, with AskUserQuestion, about each kept item that spends the user's money or time or changes what ships; the rest stand without asking. Then hand back the field and one line per kept item, as the bar the work will meet:
Bar, as <field> would set it:
- start from: <the rawest material>
- method: <a method or tool>
- aim: <the target, stated as reachable>
- right if: <the outside check>
The ask is still rough — deepening it would mean inventing what the user means → use intent skill. The user wants more options to pick from, not a higher bar for this ask → use consult 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 First seen · 29 lines · 52 tokens per session scan A 07791c9594e8
deepen is a skill published in the GitHub repository saadshahd/moo.md (37 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 447 once invoked, about $0.0002 per session on Opus 5.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-10-17.
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…
kb-lint
Health-check the knowledge bank for orphan documents, stale content, broken WikiLinks, index drift, and missing frontmatter. Generates a severity-graded report. Use this skill whenever the user mentions lint, health check, KB maintenance, stale docs, broken links, orphan pages, missing references, knowledge bank…
session-manager
Set the current session's name, project, tags, or summary on its session note. Use when the user names, tags, or summarizes this session, sets its project, or mentions in passing what this session has been about.
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.