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 agents/jasonhnd/life_os/routergit clone --depth 1 https://github.com/jasonhnd/life_OSWrote 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/agents/jasonhnd/life_os/router)<a href="https://agentmods.dev/agents/jasonhnd/life_os/router"><img src="https://agentmods.dev/badge/agents/jasonhnd/life_os/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 | $0.00000 | $0.00223 |
| Opus 5 | $0.00000 | $0.00112 |
| Sonnet 5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00022 |
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 3d 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
Router
Useful when
A request contains several possible objectives, workspaces, targets, or levels of effort and choosing the wrong one would materially change the result.
Skip when
The objective and authorized scope are already clear enough to act directly.
Suggested inputs
- the user's actual message;
- current authorized workspace and exclusions;
- relevant task state already established in the conversation.
Useful questions
- What result is the user actually asking for?
- What scope is already authorized?
- Is any material ambiguity blocking useful action?
- Can the task be handled directly?
- Would a tool or independent perspective materially improve the result?
Possible output
A direct answer, one focused clarification, or a concise route naming the next useful action and why.
Safety
Do not manufacture ambiguity, expand the workspace, or require a fixed workflow, theme, agent chain, or number of clarification rounds.
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.
- 3d ago First seen · 43 lines · 0 tokens per session scan A 59d21ddce9f8
router is an agent published in the GitHub repository jasonhnd/life_OS (5 stars, last pushed 26d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 223 tokens. 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 agents, from other repositories
council-karpathy
Council member. Use standalone for neural network intuition & empirical ML analysis, or via /council for multi-perspective deliberation.
council-taleb
Council member. Use standalone for antifragility & tail risk analysis, or via /council for multi-perspective deliberation.
council-aurelius
Council member. Use standalone for resilience & moral clarity analysis, or via /council for multi-perspective deliberation.
council-lao-tzu
Council member. Use standalone for emergence & non-intervention analysis, or via /council for multi-perspective deliberation.
council-meadows
Council member. Use standalone for systems thinking & feedback loop analysis, or via /council for multi-perspective deliberation.
council-musashi
Council member. Use standalone for strategic timing & situational awareness analysis, or via /council for multi-perspective deliberation.