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 daehounan/agency-agents-fork --skill knowledge-content-routinggit clone --depth 1 https://github.com/daehounan/agency-agents-forkWrote 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/daehounan/agency-agents-fork/knowledge-content-routing)<a href="https://agentmods.dev/skills/daehounan/agency-agents-fork/knowledge-content-routing"><img src="https://agentmods.dev/badge/skills/daehounan/agency-agents-fork/knowledge-content-routing/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/daehounan/agency-agents-fork/knowledge-content-routing"><img src="https://agentmods.dev/badge/skills/daehounan/agency-agents-fork/knowledge-content-routing.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.00120 | $0.00419 |
| Opus 5 | $0.00060 | $0.00210 |
| Sonnet 5 | $0.00024 | $0.00084 |
| Haiku 4.5 | $0.00012 | $0.00042 |
Grade A, and why
knowledge-content-routing 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 8d 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.
What it actually says
Knowledge & Content Routing Skill (Niche)
Scope intentionally narrow. For document generation by format use existing skills:
- PDF →
anthropic-skills:pdf - PPTX →
anthropic-skills:pptx - DOCX →
anthropic-skills:docx - XLSX →
anthropic-skills:xlsx - Code-generated documents with charts (mixed format) →
specialized-document-generatoragent directly
For developer documentation use existing skills:
- API reference, README, technical docs →
engineering:documentation+ecc:doc-updateragent - Internal company comms →
internal-comms/internal-comms-20260419 - Document co-authoring workflow →
doc-coauthoring - Skill creation →
anthropic-skills:skill-creator/ecc:skill-create
When to use THIS skill
Only when the work is one of these two niches:
| User signal | Agent to invoke |
|---|---|
| Luhmann-style Zettelkasten, atomic-note knowledge base, connectivity validation, knowledge graph stewardship | zk-steward |
| Enterprise training needs analysis, multi-track curriculum, internal trainer development, learning effectiveness evaluation | corporate-training-designer |
When NOT to use
Generic document generation by file format → existing anthropic-skills. Generic technical writing → existing engineering skills.
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.
- 8d ago First seen · 33 lines · 120 tokens per session scan A f6c6c8ba9610
knowledge-content-routing is a skill published in the GitHub repository daehounan/agency-agents-fork (2 stars, last pushed 3mo ago), licensed MIT. It adds 120 tokens to every session and 419 once invoked, about $0.0006 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-31.
Other skills, from other repositories
memory-review
Review the file-based memory store via the Agent Monitor Config Explorer API: the user and project CLAUDE.md plus per-project auto-memory files under /.claude/projects/ /memory/.md. Groups by project, shows the index (MEMORY.md) vs per-fact files, and flags stale or oversized facts. Reads /api/cc-config/memory and…
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
skill-status
A study-progress companion that reads a saved JSON file to remember your learning plan, progress, predictions, and past notes between sessions.
explaining-code
Explains code clearly and thoroughly. Use when asked to explain, clarify, or teach about code snippets, functions, or concepts.
session-handoff
Use when the user says "session handoff", "wrap up session", "hand off", "handoff summary", "let's wrap up", "summarize before I clear", or wants a structured end-of-session summary before clearing context. Also use proactively when the user says they are about to /clear and no handoff has been produced yet. Generates…
engineering-historian
Capture engineering knowledge as a promotion pipeline (CASE → JUDGMENT → PRINCIPLE → STANDARD) and retrieve answers from it. Capture is automatic — a post-session sweep drafts cases with status:auto; the user reviews them at /distill. Use whenever the user types "/history", "/case", or "/distill", says "log this…