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 anchorgit 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/anchor)<a href="https://agentmods.dev/skills/saadshahd/moo.md/anchor"><img src="https://agentmods.dev/badge/skills/saadshahd/moo.md/anchor/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/anchor"><img src="https://agentmods.dev/badge/skills/saadshahd/moo.md/anchor.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.00028 | $0.00216 |
| Opus 5 | $0.00014 | $0.00108 |
| Sonnet 5 | $0.00006 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
anchor 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 yesterday.
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
Find where the judgment hides: the word or clause two readers would apply differently. Replace it with something mechanical — a question with a yes/no answer, a check a machine could run, a fixture with win conditions anyone reads off the same way. Prefer the trigger a machine could evaluate over the one a careful reader could.
Silently audit the rewrite: it must decide every case the original decided, the same way. Each case it loses means you narrowed — back off by the minimum until every case fits again.
Hand back the rule with its mechanical trigger, and show it deciding one of the cases it came from so the user watches it run. Name any judgment that resisted going mechanical — that part is still open.
The complaint is coverage, not checkability → use widen skill. The cases changed, or the rule now serves a different objective → the rule needs deriving fresh, not anchoring.
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.
- yesterday Changed · -27 lines dce54daaae0a
- 9d ago First seen · 40 lines · 28 tokens per session scan A 54b3f719e271
anchor is a skill published in the GitHub repository saadshahd/moo.md (34 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 216 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
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.
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.
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…