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 agentmods add agents/vericle/intellyweave/domain-routergit clone --depth 1 https://github.com/vericle/intellyweaveWrote 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/agents/vericle/intellyweave/domain-router)<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>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.00000 | $0.01707 |
| Opus 5 | $0.00000 | $0.00853 |
| Sonnet 5 | $0.00000 | $0.00341 |
| Haiku 4.5 | $0.00000 | $0.00171 |
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.
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:
- Analyzes user query intent
- Classifies into a domain (agent name or "not-related")
- Stores classification for downstream agents
- 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
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.
- 6d ago First seen · 322 lines · 0 tokens per session scan A 64723604069c
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.
Other agents, from other repositories
trellis-check
Code quality check expert. Reviews code changes against specs and self-fixes issues.
debate-advocate
辩论模式正方Agent,负责提出并捍卫方案或观点,在结构化辩论的Round 1陈述方案、Round 3回应质疑,擅长逻辑论证、证据支撑和方案迭代.
team-member
Standard AI Team OS team member agent.
txtify-qa
QA gatekeeper for Txtify. Use to run the full verification ladder on the current tree and report evidence — before merging, releasing, or when asked "does everything still work?".
domain
This document defines the canonical domain language for Vibelution so architecture work can use stable names for the same concepts. It is intentionally small: add terms when they become load-bearing in design or tests.
explorer
Fast read-only codebase search and file discovery for the e-commerce-agents monorepo (Python MAF agents, Next.js web, .NET port). Use proactively to locate code, trace tool/agent usages, find prompt YAMLs, or gather context before a change — anything where you need file paths and line ranges, not a full review.