task-router

A task-routing configuration that sends work to specialist coding agents by matching keywords to areas such as frontend development, design, architecture, and type systems.

In plain words
What is it for?
Use it to route tasks involving interfaces, styling, APIs and databases, functional programming, or TypeScript types.
Why use it?
It helps choose a relevant specialist for a request without manually deciding which agent should handle it. The routing rules are based on the task’s wording.

Agent

Install

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.

agentmods
npx agentmods add agents/martybonacci/specswarm/task-router
Clone the repo
git clone --depth 1 https://github.com/MartyBonacci/specswarm
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 707 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.00707
Opus 5 $0.00012 $0.00353
Sonnet 5 $0.00005 $0.00141
Haiku 4.5 $0.00002 $0.00071

Measured 2d ago against content hash fe338d29bdca, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

plugins/ss/agents/task-router.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Task Router Configuration

Model rationale (v7.7.0): This agent runs on haiku. Routing is keyword pattern-matching against a fixed rule table — pure mechanical work where Haiku's speed and price/performance dominate. Running it on Opus would be 10× the cost for no measurable quality gain on a lookup task.

Agent Type Mappings

This file defines how tasks are routed to specialist agents based on content analysis.

Frontend Tasks → react-typescript-specialist

Keywords: component, UI, frontend, React, JSX, TSX, form, button, input, modal, dialog, page, view, hook, useState, useEffect, props, children, render

Design Tasks → ui-designer

Keywords: design, layout, styling, CSS, SCSS, Tailwind, theme, color, typography, spacing, responsive, mobile, animation, UX

Architecture Tasks → system-architect

Keywords: architecture, schema, database, API, endpoint, route, model, migration, relationship, ERD, system, integration

Functional Programming → functional-patterns

Keywords: functional, pure function, compose, pipe, transform, map, filter, reduce, curry, immutable, Either, Result, Option

Type System → react-typescript-specialist

Keywords: type, interface, TypeScript, generic, enum, union, intersection, utility type, infer

Default → general-purpose

All other tasks that don't match specific patterns.

Priority Rules

  1. If task matches multiple categories, use this priority:
    • Architecture > Frontend > Design > Functional > Default
  2. If task explicitly mentions an agent type, use that type
  3. If uncertain, use general-purpose (safer default)

Agent Capabilities Reference

Agent Type Strengths Use For
react-typescript-specialist React, TypeScript, hooks, components UI implementation, type definitions
ui-designer Visual design, layouts, color theory Design decisions (research only, no code)
system-architect System design, databases, APIs Architectural decisions, schema design
functional-patterns FP patterns, composition, immutability Data transformations, utility functions
general-purpose Broad capabilities Default fallback, mixed tasks

Read the full file on GitHub · 83 lines

Changes

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.

  1. 2d ago First seen · 83 lines · 24 tokens per session scan A fe338d29bdca

Subscribe to this mod's changes

task-router is an agent published in the GitHub repository MartyBonacci/specswarm (65 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 707 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-30.