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.
git clone --depth 1 https://github.com/Khar-AG/t-800-agentWrote 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/rules/khar-ag/t-800-agent/t-800-factory-routing)<a href="https://agentmods.dev/rules/khar-ag/t-800-agent/t-800-factory-routing"><img src="https://agentmods.dev/badge/rules/khar-ag/t-800-agent/t-800-factory-routing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/khar-ag/t-800-agent/t-800-factory-routing"><img src="https://agentmods.dev/badge/rules/khar-ag/t-800-agent/t-800-factory-routing.svg" alt="Reviewed on agentmods" width="80" 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.00065 | $0.00343 |
| Opus 5 | $0.00032 | $0.00171 |
| Sonnet 5 | $0.00013 | $0.00069 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
t-800-factory-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.
What it actually says
T-800 Factory — маршрутизация
Когда вызывать Task(t-800-factory)
- Пользователь хочет создать нового субагента
- Проектирование большого плагина с множеством агентов
- Вопросы: subagent vs skill, routing, registry, связи между агентами
- Явный вызов:
/t-800-factory, «отдел субагентов», «T-800 Factory» - После идеи нового агента — всегда через Factory pipeline
Когда НЕ вызывать
- Обучение новичка Cursor →
Task(t-800-operator) - Обновление KB T-800 →
Task(t-800-maintainer) - Пользователь просит просто выполнить задачу без создания агента
Пайплайн
Task(t-800-scout) → Task(t-800-brain-lead) → Task(t-800-factory) → architect → builder → integrator → auditor
См. также rules/t-800-mandatory-routing.mdc (alwaysApply).
KB
knowledge-base/13-agent-factory/INDEX.mdknowledge-base/14-t-800-brains/INDEX.md
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 · 37 lines · 65 tokens per session scan A 50f5b9249321
t-800-factory-routing is a cursor rule published in the GitHub repository Khar-AG/t-800-agent (8 stars, last pushed 14d ago), licensed MIT. It adds 65 tokens to every session and 343 once invoked, about $0.0003 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-09-03.
Other cursor rules, from other repositories
pn-aesthetics-baseline
Non-generic UI baseline for user-facing surfaces; aligns with .pncore-design.md and pn-core aesthetics reference when MCP is available.
pn-build-gate
For build/design/scaffold requests, load pn-build or pn-design; discovery and skeptic mandatory. For fix/tweak, use skills directly.
pn-godot
Godot 4.x coding conventions: GDScript typing, signal patterns, scene composition, shader style, naming, Resource patterns, multiplayer RPC safety, GDExtension registration. Use when editing .gd, .tscn, .tres, .gdshader, or project.godot files.
pn-nextjs
Next.js best practices. Data loading, server/client boundaries, streaming, mutations, and performance. For Next app/ or pages/, pn-react also applies (core React patterns); content is complementary.
pn-mcp-proactive
When MCP is available, use pn-core tools proactively when tasks match pn skills or agents; use Octocode for code research when available.
pn-php-backend
PHP backend style, env, and error handling. Use for API and server code (Laravel, Slim).