agentmods.dev

t-800-mandatory-routing

t-800-mandatory-routing is a cursor rule for Cursor from Khar-AG/t-800-agent. It costs 1,682 tokens per session, scanned A, original, MIT.

A mandatory routing rule for creating or changing subagents, skills, commands, rules, and hooks. Hooks are scripts that run automatically when certain events occur.

In plain words
What is it for?
It helps enforce the approved workflow for building or modifying agents, skills, commands, rules, hooks, and their validation scripts.
Why use it?
It prevents these project control files from being edited directly in the main chat and requires them to pass through the T-800 Factory process.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

not rated 8repo 14d ago A scan 1,682 tokens original MIT

Good fit It helps enforce the approved workflow for building or modifying agents, skills, commands, rules, hooks, and their validation scripts.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/khar-ag/t-800-agent/t-800-mandatory-routing
View source ↗ Khar-AG/t-800-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.

Clone the repo
git clone --depth 1 https://github.com/Khar-AG/t-800-agent

Made for: Cursor.

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 t-800-mandatory-routing

README.md
[![agentmods](https://agentmods.dev/badge/rules/khar-ag/t-800-agent/t-800-mandatory-routing/github.svg)](https://agentmods.dev/rules/khar-ag/t-800-agent/t-800-mandatory-routing)
Your own site
<a href="https://agentmods.dev/rules/khar-ag/t-800-agent/t-800-mandatory-routing"><img src="https://agentmods.dev/badge/rules/khar-ag/t-800-agent/t-800-mandatory-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.

agentmods 80×15 button for t-800-mandatory-routing

Your own site · 80×15
<a href="https://agentmods.dev/rules/khar-ag/t-800-agent/t-800-mandatory-routing"><img src="https://agentmods.dev/badge/rules/khar-ag/t-800-agent/t-800-mandatory-routing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,682 This file is loaded in full into every session.
When invoked 1,682 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.01682 $0.01682
Opus 5 $0.00841 $0.00841
Sonnet 5 $0.00336 $0.00336
Haiku 4.5 $0.00168 $0.00168

Measured 7d ago against content hash 69645b49f1c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

t-800-mandatory-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.

rules/t-800-mandatory-routing.mdc · 122 lines

How it starts

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

T-800 Agent — обязательная маршрутизация конвейера

BLOCKER (Директор / main chat)

Запрещено в main chat (и любому оркестратору вне factory):

  • Write / StrReplace / прямые правки файлов в agents/, skills/**/SKILL.md, commands/, rules/*.mdc, hooks.json, hooks/*
  • «Implement the plan» с правкой этих путей, если в плане есть factory-brief / /t800-start / /t800-fix

Разрешено только: Task(t-800-factory) (через /t800-start или /t800-fix).
Контракт Plan→Implement: shared/plan-to-factory-handoff-contract.md.

Rule = advisory для агента. Жёсткий FAIL — machine gates:
scripts/t800_factory_bypass_gate.py, scripts/t800_run_gate.py --strict-create.
Hook preToolUse (hooks/before-artifact-edit.sh, artifact-edit guard) в v1 даёт WARN, не hard-deny.

Когда ВСЕГДА через T-800

  • Создать, изменить или удалить субагента (agents/*.md)
  • Создать или изменить skill (.cursor/skills/)
  • Создать или изменить command (.cursor/commands/)
  • Создать или изменить rule (.cursor/rules/*.mdc)
  • Создать или изменить hook (hooks.json, .cursor/hooks/)
  • Скрипты установки/валидации плагина (scripts/validate-agents.*, scripts/t800_run_gate.py и т.д.)
  • Вопрос «как правильно в Cursor» при проектировании артефактов

Обязательная цепочка (v1.13 — отделы + loop + fix)

flowchart LR
    task[Задача]
    intake[intake?]
    scout[scout]
    research[research-lead]
    craft[prompt-craft?]
    brain[brain-lead]
    factory[factory]
    task --> intake --> scout --> research --> craft --> brain --> factory

Директор зовёт только лидов. Специалисты — авто внутри лида
(shared/department-orchestration-contract.md).

  1. intake-clarifier? → scout
  2. research-lead → АВТО strategist → specialists → synthesizer
  3. prompt-craft? (agent/skill/command)
  4. brain-lead → АВТО 1–2 domain brains
  5. factory → АВТО architect → … → auditor

Правка существующего: /t800-fix (fix-pack → SKIP/LIGHT → factory PATCH → t800_run_gate.py).
Контракт: shared/fix-pipeline-contract.md.

Read the full file on GitHub · 122 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. 7d ago First seen · 122 lines · 1,682 tokens per session scan A 69645b49f1c6

Subscribe to this mod's changes

t-800-mandatory-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 1,682 tokens to every session, about $0.0084 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.

Building agentsagentscursorpluginskynett-800
Related

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.

perniemann/pnCore · 447 tokens

pn-build-gate

For build/design/scaffold requests, load pn-build or pn-design; discovery and skeptic mandatory. For fix/tweak, use skills directly.

perniemann/pnCore · 1,736 tokens

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.

perniemann/pnCore · 1,156 tokens

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.

perniemann/pnCore · 1,111 tokens

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.

perniemann/pnCore · 0 tokens

pn-php-backend

PHP backend style, env, and error handling. Use for API and server code (Laravel, Slim).

perniemann/pnCore · 0 tokens