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/phuonghx/aim-cli/intelligent-routingnpx skills add phuonghx/aim-cli --skill intelligent-routinggit clone --depth 1 https://github.com/phuonghx/aim-cliWhat 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.00098 | $0.01606 |
| Opus 5 | $0.00049 | $0.00803 |
| Sonnet 5 | $0.00020 | $0.00321 |
| Haiku 4.5 | $0.00010 | $0.00161 |
Grade A, and why
intelligent-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 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intelligent Routing
Treat every request the way a good project manager would: read it, figure out which expert should own it, and hand it over — without making the user learn the org chart. Routing happens silently and continuously; the user just gets the right specialist's answer.
The Flow For Every Request
Before producing any reply, run a quick mental pass:
incoming request
→ read the intent (what kind of ask is this?)
→ tag the domains it touches
→ judge how big it is
→ pick the agent(s) and apply their expertise
Done well, this costs almost nothing and saves the round-trips that come from a generalist guessing at a specialist's job.
Picking The Agent
Match the request's signal words to a specialist. The right-hand column says whether to act immediately or pause for a quick confirmation first.
| The ask is about | Tell-tale words | Send it to | Act now? |
|---|---|---|---|
| Sign-in / accounts | login, auth, signup, password | security-auditor + backend-specialist |
yes |
| A UI piece | button, card, layout, style | frontend-specialist |
yes |
| A mobile surface | screen, navigation, gesture, touch | mobile-developer |
yes |
| An HTTP route | endpoint, route, GET, POST | backend-specialist |
yes |
| Data layer | schema, migration, query, table | database-architect + backend-specialist |
yes |
| Something broken | error, bug, broken, not working | debugger |
yes |
| Tests | test, coverage, unit, e2e | test-engineer |
yes |
| Shipping | deploy, production, CI/CD, docker | devops-engineer |
yes |
| A security pass | vulnerability, exploit, hardening | security-auditor + penetration-tester |
yes |
| Speed | slow, optimize, latency, cache | performance-optimizer |
yes |
| Product shaping | requirements, user story, MVP | product-owner |
yes |
| A whole feature | build, create, implement, new app | orchestrator → many agents |
confirm first |
| Many domains at once | spans several areas | orchestrator → many agents |
confirm first |
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 · 126 lines · 98 tokens per session scan A 78a56972b6a6
intelligent-routing is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 2mo ago), licensed MIT. It adds 98 tokens to every session and 1,606 once invoked, about $0.0005 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
hs-release
Cut a core Hindsight release (vX.Y.Z) and open the changelog + blog PR. Use when asked to cut/start a release, bump the version, or publish a new Hindsight version.
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
survey-design
Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use a-b-test-design (prototyping-testing).
design-critique
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use heuristic-evaluation (prototyping-testing).
design-sprint-plan
Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use team-workflow.
handoff-spec
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use design-qa-checklist; for reusable library components use component-spec (design-systems).