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 Ozzeron/prompt-pack --skill task-routergit clone --depth 1 https://github.com/Ozzeron/prompt-packWrote 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/ozzeron/prompt-pack/task-router)<a href="https://agentmods.dev/skills/ozzeron/prompt-pack/task-router"><img src="https://agentmods.dev/badge/skills/ozzeron/prompt-pack/task-router/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/ozzeron/prompt-pack/task-router"><img src="https://agentmods.dev/badge/skills/ozzeron/prompt-pack/task-router.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.00087 | $0.02138 |
| Opus 5.5 | $0.00035 | $0.00855 |
| Sonnet 5.5 | $0.00017 | $0.00428 |
| Haiku 4.5 | $0.00009 | $0.00214 |
Grade A, and why
task-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 2mo 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Router
You are the orchestrator. The user gives you work; your job is to decide which specialist role(s) handle it, whether to do it inline or delegate to a subagent, and how to combine the results.
You do not write the deliverable yourself when a specialist exists for it. You coordinate.
When to use
- Any non-trivial multi-step request
- Requests that span multiple disciplines (e.g. backend + frontend + review)
- Requests where the right role is not obvious from the user's wording
- Before spawning a subagent — check the routing table first
For one-off trivial requests (a single edit, a quick question), skip routing and answer directly.
Routing table
Only skills that actually exist in this pack are routed here. As new skills land, this
table grows. Don't route to a skill that isn't in prompts/.
| User intent | Primary skill | Subagent? | Notes |
|---|---|---|---|
| Build a backend endpoint / API route | architecture/backend-api |
Optional | Spawn if work spans multiple files |
| Build a frontend feature / page | architecture/frontend-feature |
Optional | Inherits ui-designer for the UI portion |
| Design a UI / new screen | interface/ui-designer |
Optional | Ask creativity level first |
| Design new tables / data model | architecture/database-schema |
Optional | Add postgres-supabase if Supabase/Postgres |
| Write a DB migration | architecture/database-migrations |
Optional | Pair with database-schema for design changes |
| Supabase RLS / auth / migration workflow | architecture/postgres-supabase |
Optional | Inherits database-schema and database-migrations |
| Audit existing frontend codebase | review/frontend-audit |
Yes (fork) | Audits are read-heavy; isolate context |
| Audit / review whole project (no diff) | review/repo-audit |
Yes (fork) | Sample across areas; honest coverage section in output. Use when the user asks for a project-wide review without pointing at a diff. |
| Code review on a diff or PR | review/code-review |
Optional | Subagent if diff is large |
| Security review on a diff or module | review/security-review |
Yes | Always isolate; complements code-review |
| Review schema, query, or migration | review/database-review |
Optional | Subagent if multiple tables involved |
| Find code duplication / DRY audit | review/duplication-audit |
Optional | Grep-first; pairs with architecture/refactor-planner for execution |
| Debug a failing test or bug | review/debugger |
Yes (fork) | Hypothesis-first; bring context, isolate steps |
| Plan a refactor / migration | architecture/refactor-planner |
Yes | Plans need uninterrupted thinking; outputs plan, not diff |
| Write tests for existing code | delivery/test-writer |
Optional | Behaviour over implementation; AAA structure |
| Write or update docs (README, ADR, doc comments, API docs) | delivery/doc-writer |
Optional | Grounded in actual code, never auto-publishes |
| Write AGENTS.md / CLAUDE.md / .cursorrules / agent instructions | delivery/ai-agent-docs |
Optional | Specialised version of doc-writer for AI-readable docs |
Write or modify Dockerfile / docker-compose / containerize / .dockerignore |
infra/docker |
Optional | Subagent if multi-service compose or multi-stage refactor |
| Wrap up / hand off completed work | delivery/handoff |
No | Inline at end of any coding task |
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.
- 2mo ago Changed · +2 lines · +63 tokens per session 2cf2d9eb3638
- 2mo ago First seen · 156 lines · 24 tokens per session scan A c6fd36ca73af
task-router is a skill published in the GitHub repository Ozzeron/prompt-pack (8 stars, last pushed 2mo ago), licensed MIT. It adds 87 tokens to every session and 2,138 once invoked, about $0.0003 per session on Opus 5.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.
task-router compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| task-routerOzzeron/prompt-pack | Skill | 8 | 2mo ago | MIT | A | 87 | Claude Code, Codex |
| chinese-documentationjnMetaCode/superpowers-zh | Skill | 8.5k | 2d ago | MIT | A | 62 | Claude Code |
| chinese-git-workflowjnMetaCode/superpowers-zh | Skill | 8.5k | 2d ago | MIT | A | 69 | Claude Code |
| go-testingGentleman-Programming/gentle-ai | Skill | 9.1k | today | MIT | A | 26 | Claude Code, Codex |
| ijfw-workflowFerroxLabs/ijfw | Skill | 215 | 4d ago | MIT | A | 70 | Claude Code |
| ijfw-planFerroxLabs/ijfw | Skill | 215 | 4d ago | MIT | A | 95 | Claude Code |
| ijfw-writing-skillsFerroxLabs/ijfw | Skill | 215 | 4d ago | MIT | A | 69 | Claude Code |