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 hajekim/agentic-design-patterns-extension --skill routinggit clone --depth 1 https://github.com/hajekim/agentic-design-patterns-extensionWrote 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/hajekim/agentic-design-patterns-extension/routing)<a href="https://agentmods.dev/skills/hajekim/agentic-design-patterns-extension/routing"><img src="https://agentmods.dev/badge/skills/hajekim/agentic-design-patterns-extension/routing.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.1 | $0.00391 | $0.03174 |
| Opus 5 | $0.00196 | $0.01587 |
| Sonnet 5 | $0.00078 | $0.00635 |
| Haiku 4.5 | $0.00039 | $0.00317 |
Grade A, and why
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 7d 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.
This is a copy
100% identical to routing — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Routing Pattern
Overview
The Routing Pattern introduces conditional logic into an agent's operational framework, enabling dynamic decision-making about which specialized function, tool, or sub-agent should handle a given input. Rather than following a fixed linear execution path, a routing agent first analyzes the input to determine its intent or nature, then directs it to the most appropriate handler.
Core Principle: Analyze first, then dispatch — transform a static executor into a dynamic, context-aware system.
When This Skill Applies
Activate this pattern when:
- An agent must decide between multiple distinct workflows, tools, or sub-agents
- Incoming requests vary significantly in type, intent, or required handling
- A system needs to triage or classify inputs before processing
- Different user intents require fundamentally different processing paths
- A static sequential flow cannot handle the variability of real-world inputs
Rule of thumb: Use Routing when an agent must intelligently choose the best possible action from a set of options based on input characteristics.
DEFINE → PLAN → ACTION Workflow
DEFINE
Map the decision space:
- What are the distinct categories or intents of incoming requests?
- What handler, tool, or sub-agent is optimal for each category?
- What routing mechanism is most appropriate (LLM, embedding, rule-based)?
- What is the fallback for unclear or uncategorized inputs?
PLAN
Design the routing architecture:
- Define the router component (LLM prompt, embedding comparator, or rule engine)
- Define each destination handler with clear responsibility boundaries
- Design the routing decision prompt or logic
- Plan the fallback/clarification pathway for ambiguous inputs
- Decide routing placement: at entry, mid-chain, or sub-routine selection
ACTION
Implement the routing system:
- Build the router that classifies input and outputs a destination identifier
- Create specialized handlers for each route
- Wire the router output to the appropriate handler selection logic
- Test with representative inputs across all categories and edge cases
- Implement fallback handling and monitoring of routing decisions
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.
- 7d ago First seen · 322 lines · 391 tokens per session scan A e069b00c7864
routing is a skill published in the GitHub repository hajekim/agentic-design-patterns-extension (1 stars, last pushed 5mo ago), licensed MIT. It adds 391 tokens to every session and 3,174 once invoked, about $0.0020 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to routing, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
prompt engineering
Use this skill when asked to create, refine, analyze, or optimize prompts for Large Language Models (LLMs). This skill ensures adherence to prompt engineering best practices and enforces a rigorous design workflow.
redteam
Expertise in offensive security research, vulnerability analysis, CMS-focused application testing, and red team operations.
redteam-source-audit
Focused source-code security review workflow for web applications, CMS extensions, APIs, and supporting services.
redteam-cms
Focused methodology for authorized CMS fingerprinting, component inventory, misconfiguration review, and vulnerability validation.
redteam-exploit-validation
Focused workflow for validating exploitability safely and turning candidate issues into reproducible, bounded proof.
redteam-recon
Focused reconnaissance workflow for authorized security assessments, bug bounty triage, lab targets, and CTF infrastructure.