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 HoangNguyen0403/agent-skills-standard --skill common-task-complexity-routinggit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/common-task-complexity-routing)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/common-task-complexity-routing"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-task-complexity-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/hoangnguyen0403/agent-skills-standard/common-task-complexity-routing"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-task-complexity-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.00068 | $0.01414 |
| Opus 5.5 | $0.00027 | $0.00566 |
| Sonnet 5.5 | $0.00014 | $0.00283 |
| Haiku 4.5 | $0.00007 | $0.00141 |
Grade A, and why
common-task-complexity-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 today.
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Complexity Routing (SNC)
Priority: P1 (HIGH)
Same ticket label, different engineering difficulty. Score the task, not the label, then route by tier.
Score
| Dimension | 0 | 1 | 2 |
|---|---|---|---|
| Spread (how far the change reaches) | one file, one module | several files, one module | cross-module or cross-service |
| Novelty (new vs existing behavior) | small edit or removal of existing behavior | modify existing logic | new behavior or rewrite |
| Centrality (how core the touched code is) | peripheral code | shared but non-core | core domain, hot path, auth, money, trust boundary |
Sum the three, never average. Output line: SNC: S=[0-2] N=[0-2] C=[0-2] total=[n] tier=[low|medium|high].
Tiers
tier=low: total 0-2tier=medium: total 3-4tier=high: total 5-6
Routing
| Tier | Autonomy | Verification | Review | Approval | model_tier |
|---|---|---|---|---|---|
tier=low |
autonomous | basic: focused tests + lint | fast code-review |
none required | fast |
tier=medium |
guided | TDD + self-review | deep code-review |
plan reviewed, no HARD STOP | standard |
tier=high |
plan-first | TDD + independent reviewers (specialist-architecture-guard, specialist-security-reviewer when relevant) |
deep code-review |
HARD STOP before code, human approval before merge | strong |
fast | standard | strong is a capability hint only. Each host maps it to its model ladder and binds the named review roles to its own invocation mechanism; the hint is not authorization: premium spend, account selection and execution mode remain host/human decisions.
Capability and Effort
Capability and thinking effort are independent dimensions. Recommend the least expensive eligible configuration adequate for the task and its verification burden; never simply the cheapest model. The host resolves eligibility, approved profiles, supported effort and authorized fallback.
- Deterministic operation uses an existing tool, script or CLI before any LLM call; bounded implementation uses tier-appropriate capability with focused tests.
- Ambiguous investigation: wider effort, because premature narrowing costs more than the extra reasoning.
- Consequential review: capable model plus an independent reviewer; a small diff never lowers a sensitivity floor.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +20 lines · -3 tokens per session f1baa612d39e
- yesterday Changed · +3 lines e7e3231f3d9a
- 20d ago Changed · +7 lines ae8554705a11
- 1mo ago First seen · 70 lines · 71 tokens per session scan A 0d4c05d79922
common-task-complexity-routing is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (582 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 1,414 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-09-14.
Other skills, from other repositories
nextjs-idioms
Next.js App Router architecture: React Server Components (RSC), Server Actions, nested layouts, route handlers, and streaming. Use when building or refactoring Next.js web applications. Pair with react-idioms and typescript-idioms.
react-idioms
React 19+ patterns: custom hooks, Suspense boundaries, state management, component composition, and web performance. Use when developing or refactoring React components and client applications. Pair with typescript-idioms.
elite-engineer
The operating system for elite software engineering in TypeScript, React, and Next.js. Enforces the cognitive models, architecture laws, type-level patterns, component design, visual standards, and performance mandates that separate exceptional software from the ordinary — grounded in named sources (Torvalds…
oma-frontend
Implement or modify web UI in React, Next.js, or Angular. Use for components, pages, styles, forms, and frontend state or data flows.
design-patterns
Frontend design patterns with React 19.2 and TypeScript 6 examples (Composition, Compound Components, Custom Hooks, Render Props, HOC, State Machines). Use when user asks "implement pattern", "use composition", or when designing reusable components.
react-nextjs
React 19.2 + Next.js 16 development - Server Components, Cache Components, proxy.ts, View Transitions, App Router, TypeScript 6, and Tailwind CSS v4. Use when building frontend apps, creating components, or asking "how do I set up X?".