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/indexgit clone --depth 1 https://github.com/vericle/intellyweaveWhat 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 | $0.00000 | $0.02139 |
| Opus 5 | $0.00000 | $0.01069 |
| Sonnet 5 | $0.00000 | $0.00428 |
| Haiku 4.5 | $0.00000 | $0.00214 |
Grade A, and why
index 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 3d 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.
Agents and Domain Router
Specialized tools and intelligent query routing for domain-specific intelligence analysis.
What It Does
IntellyWeave's agent system provides two capabilities:
- Domain Router: Classifies user queries and routes them to appropriate specialized agents
- Specialized Agents: System and custom agents that handle domain-specific queries
User Query → Domain Router → Classification → Specialized Agent → Response
This system enables:
- Automatic routing to the right agent based on query intent
- Custom agents with user-defined knowledge bases
- System agents for common tasks (entity extraction, geocoding, personalization)
- Decision tree integration where agents act as Tools
Use When
- You need specialized handling for specific query types
- You want to create custom agents with dedicated knowledge bases
- You need entity extraction, geocoding, or personalization
- You want automatic routing without manual agent selection
Agent Categories
IntellyWeave has two categories of agents:
System Agents (Option A: Decision Tree Tools)
Always-available tools that the decision tree can invoke directly:
| Agent | Purpose | Inputs |
|---|---|---|
| QueryExtractorTool | Extracts and enriches entities from documents | query, documents |
| GeospatialTransformationTool | Geocodes locations and creates virtual documents | entities, user_interest, operation_mode |
| PersonalizationTool | Adjusts workflow based on user preferences | query, user_id |
Custom User Agents (Option B: Router-Accessible)
User-defined agents that the Domain Router can select:
| Agent | Purpose | Selection Criteria |
|---|---|---|
| PersonalizationAgent | Workflow customization via router | Query involves preferences |
| Custom Agents | User-uploaded knowledge bases | Query matches agent domain |
How the System Works
Query Flow
1. User submits query
2. Domain Router analyzes query intent
3. Router classifies into domain (agent name or "not-related")
4. Classification stored in hidden_environment
5. Matching agent's is_tool_available() returns True
6. Agent processes query and returns response
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.
- 3d ago First seen · 322 lines · 0 tokens per session scan A ddfd4db293a4
index is an agent published in the GitHub repository vericle/intellyweave (75 stars, last pushed 7mo ago), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 2,139 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
agent-request-queue
一次 Agent 运行可能包含多次模型调用、知识库检索、工具执行和文件操作。为了避免同一对话同时修改同一份上下文，Yuxi 把“收到请求”和“开始运行”分成两个阶段，并为每个线程维护 FIFO 队列。.
plan
分析研究需求，建立覆盖模型，拆解可执行研究任务，规划数据源和执行顺序.
trellis-check
Code quality check expert. Reviews code changes against specs and self-fixes issues.
sre
站点可靠性工程师，负责系统可用性保障、事故响应、容量规划、SLO/SLI定义和自动化运维.
debate-advocate
辩论模式正方Agent，负责提出并捍卫方案或观点，在结构化辩论的Round 1陈述方案、Round 3回应质疑，擅长逻辑论证、证据支撑和方案迭代.
team-member
Standard AI Team OS team member agent.