domain-router

domain-router is an agent for Claude Code from vericle/intellyweave. It costs 0 tokens per session (1,707 once invoked), scanned A, original, BSD-3-Clause.

A component that classifies a user’s request into a relevant subject area and routes it to a specialized agent. It runs once per request and stores the classification for later steps.

In plain words
What is it for?
Use it to inspect the request, select an available domain agent, and record whether the request belongs to a supported domain.
Why use it?
It helps choose the right specialist when several custom agents are available and avoids repeatedly routing the same request.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

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/vericle/intellyweave/domain-router
Clone the repo
git clone --depth 1 https://github.com/vericle/intellyweave

Made for: Claude Code.

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

agentmods badge for domain-router

README.md
[![agentmods](https://agentmods.dev/badge/agents/vericle/intellyweave/domain-router.svg)](https://agentmods.dev/agents/vericle/intellyweave/domain-router)
Your own site
<a href="https://agentmods.dev/agents/vericle/intellyweave/domain-router"><img src="https://agentmods.dev/badge/agents/vericle/intellyweave/domain-router.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,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.1 $0.00000 $0.01707
Opus 5 $0.00000 $0.00853
Sonnet 5 $0.00000 $0.00341
Haiku 4.5 $0.00000 $0.00171

Measured 6d ago against content hash 64723604069c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

domain-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 6d 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.

docs/guides/agents/domain-router.md · 322 lines

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.

Domain Router

Intelligent query classification that routes user queries to specialized agents.

What It Does

The Domain Router is a Tool that:

  1. Analyzes user query intent
  2. Classifies into a domain (agent name or "not-related")
  3. Stores classification for downstream agents
  4. Runs once per query to prevent infinite loops
User Query → Domain Router → Classification → Agent Selection

Use When

The Domain Router is automatically invoked when:

  • Custom agents are available for the user
  • Query may require specialized knowledge
  • Decision tree evaluates available tools

How It Works

Classification Flow

1. Router receives user query
2. Loads custom agent names and descriptions from hidden_environment
3. Creates dynamic prompt with available domains
4. LLM classifies query into one domain
5. Stores classification in hidden_environment
6. Subsequent agents check classification

One-Time Execution

The router only runs once per query:

async def is_tool_available(self, tree_data, ...):
    # Check if classification already exists
    classification_exists = (
        "domain_classification" in tree_data.environment.hidden_environment
    )
    # Only available if no classification yet
    return not classification_exists

This prevents infinite loops where the router would run on every decision tree iteration.

Classification Output

The router produces a DomainClassification result:

DomainClassification(
    domain="Immigration Law Expert",  # or "not-related"
    reasoning="Query asks about visa requirements which matches Immigration Law Expert",
    confidence="high"  # or "medium", "low"
)

Storage Location

Classification is stored in hidden_environment:

tree_data.environment.hidden_environment["domain_classification"] = {
    "domain": "Immigration Law Expert",
    "reasoning": "Query asks about visa requirements...",
    "confidence": "high"
}

Valid Domains

Read the full file on GitHub · 322 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. 6d ago First seen · 322 lines · 0 tokens per session scan A 64723604069c

Subscribe to this mod's changes

domain-router is an agent published in the GitHub repository vericle/intellyweave (75 stars, last pushed 3d ago), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 1,707 tokens. 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.