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 sefaertunc/Worclaude --skill agent-routinggit clone --depth 1 https://github.com/sefaertunc/WorclaudeWrote 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/sefaertunc/worclaude/agent-routing)<a href="https://agentmods.dev/skills/sefaertunc/worclaude/agent-routing"><img src="https://agentmods.dev/badge/skills/sefaertunc/worclaude/agent-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.00010 | $0.01928 |
| Opus 5 | $0.00005 | $0.00964 |
| Sonnet 5 | $0.00002 | $0.00386 |
| Haiku 4.5 | $0.00001 | $0.00193 |
Grade A, and why
agent-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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Routing Guide
Read this file at the start of every session. It tells you which agents are available and when to use them.
How Agents Work
- Agents are specialist subprocesses. Spawn them to keep your main context clean.
- Worktree agents run in isolation — safe to run in parallel with your work.
- Non-worktree agents share your context — don't edit the same files they're reading.
- Never spawn more than 3 agents simultaneously.
- If a task is small enough to do yourself in 2 minutes, don't spawn an agent for it.
Background-Agent Concurrency
Two background agents on the same branch coexist cleanly:
- Worktree-isolated agents (
isolation: "worktree") each create their own sibling worktree offorigin/HEAD. They never collide on files, refs, or the index — running multiple in parallel is safe by design. - Non-isolated agents share the main checkout but are read-only by convention. The main session and these agents must avoid editing the same files concurrently; otherwise behavior is up to whoever writes last.
Worktree lock semantics: Claude Code locks each agent worktree with the agent's
pid; the lock survives agent completion. Stale locks are normal. Clean up with
git worktree remove -f -f <path> or the project's worktree-cleanup helper.
The earlier "lock file per branch" plan was rejected after the 2026-04-26 concurrency test — worktree isolation already provides the guarantee a lock file would have, and a lock would block the legitimate parallel-agents case.
Automatic Triggers
These agents should be spawned without being asked when their trigger condition is met.
build-validator
- Model: Haiku | Isolation: None
- When: Before every commit. After merging worktree branches.
- Trigger: Automatic — spawn when trigger condition is met
- What it does: Quick validation — tests pass, build succeeds, lint clean. Fast and cheap (Haiku model).
- Expect back: Pass/fail with specific errors if failed.
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 · 170 lines · 10 tokens per session scan A 1d8beec18ad0
agent-routing is a skill published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 28d ago), licensed MIT. It adds 10 tokens to every session and 1,928 once invoked, about $0.0001 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
unicli-repair
Evidence-driven repair workflow for a broken Uni-CLI adapter. Trigger on a failed unicli envelope, a quarantined adapter, or an explicit adapter-repair request. Classifies non-source failures, edits only the reported adapter path, and uses the original command as a bounded oracle.
autonomous-run
Prepare, start, inspect, resume, or stop a finite local overnight coding run after a human has accepted a Wayfinder terminal spec; coordinates a declared Claude/Codex maker and independent checker without pushing, merging, or writing to external systems.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.
i18n-localization
Internationalization and localization for global applications. Use when adding multi-language support, handling regional formats, or preparing apps for global markets.
electron-desktop
Desktop application development with Electron for Windows, macOS, and Linux. Use when building cross-platform desktop apps, implementing native OS features, or packaging web apps for desktop.