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/grainulation/grainulator/routernpx skills add grainulation/grainulator --skill routergit clone --depth 1 https://github.com/grainulation/grainulatorWhat 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.00019 | $0.00618 |
| Opus 5 | $0.00010 | $0.00309 |
| Sonnet 5 | $0.00004 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
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 2d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/router -- Intent Router
Routes plain-language user messages to the appropriate grainulator skill.
Intent Map
| User says something like... | Route to | Why |
|---|---|---|
| "look into X", "what about X", "explore X" | /research X |
Information gathering |
| "build X", "try X", "make a quick X" | /prototype |
Hands-on validation |
| "is p001 really true?", "I doubt X" | /challenge <id> |
Adversarial testing |
| "check this: ", "does support X" | /witness <id> <url> |
External corroboration |
| "what are we missing", "any gaps?" | /blind-spot |
Structural gap analysis |
| "where are we", "what's the status" | /status |
Sprint snapshot |
| "write it up", "summarize for the team" | /brief |
Decision document |
| "make slides", "prepare for the meeting" | /present |
Stakeholder presentation |
| "publish to confluence", "sync to confluence", "push to wiki" | /sync |
Confluence publish |
| "pull from confluence", "import from wiki", "backfill from confluence" | /pull <slug> |
Confluence pull |
| "show the plan", "what sprints are next", "dependency graph" | /orchard |
Multi-sprint orchestration |
| "show analytics", "how healthy is this sprint", "stale claims" | /harvest |
Sprint analytics |
| "fetch this url", "what does <url> say", "summarize <url>" | /fetch <url> |
Size-efficient URL fetch |
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.
- 2d ago First seen · 45 lines · 19 tokens per session scan A 2e48191529d4
router is a skill published in the GitHub repository grainulation/grainulator (86 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 618 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
workflow
Professional AI programming assistant with structured workflow (Research -> Ideate -> Plan -> Execute -> Optimize -> Review) for developers.
r3f-animation
React Three Fiber animation - useFrame, useAnimations, spring physics, keyframes. Use when animating objects, playing GLTF animations, creating procedural motion, or implementing physics-based movement.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
golden-rss
Use when testing the rss golden build.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.