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/chf3198/copilot-governance/router-policygit clone --depth 1 https://github.com/chf3198/copilot-governanceWrote 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/chf3198/copilot-governance/router-policy)<a href="https://agentmods.dev/agents/chf3198/copilot-governance/router-policy"><img src="https://agentmods.dev/badge/agents/chf3198/copilot-governance/router-policy.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.00695 |
| Opus 5 | $0.00000 | $0.00347 |
| Sonnet 5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
router-policy 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 5d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Router Policy Spec v1.0.0
Routing Principles
- Prefer deterministic constraints before any score-based choice.
- Prefer the lowest-capable tier that can still satisfy the task.
- Treat empirical scores as a tie-breaker and fallback signal.
- Treat rate limits, offline providers, and sensitivity constraints as hard stops.
Hard Constraints
- Privacy or local-only requirement → avoid cloud-only providers.
- Availability or rate-limit failure → skip the candidate.
- Context or tool requirements not met → skip the candidate.
- Ambiguous scope or multi-solution request → route to
planner.
Ranking Signals
- Task fit: security, implementation, quick lookup, or design complexity.
- Empirical quality: controlled eval score or proven provider performance.
- Cost class: choose the cheapest option that clears the quality bar.
- Latency and throughput: prefer fast tiers when the task is latency-sensitive.
- Risk: prefer higher-control tiers for security-sensitive or high-impact work.
Minimum Task Metadata
- Intent class
- Sensitivity or privacy level
- Context length expectation
- Latency budget
- Tool-use requirement
- Offline/local execution requirement
Fallback Guidance
- Pick the best-fit tier from the classification rules.
- If the preferred model or provider is unavailable, fall back to the next best empirical option that satisfies the hard constraints.
- If the task is still ambiguous after filtering, choose
planner.
Decision Rule
If the request is simple and low-risk, route to quick.
If it is a clear implementation task, route to implementer.
If it is high-risk, architectural, or security-sensitive, route to architect.
If it needs clarification or multi-step planning, route to planner.
Implementation
This policy is implemented in scripts/global/task-router-policy.json and scripts/global/task-router.js.
{
"version": "1.0.0",
"defaultLane": "free",
"lanes": {
"free": {
"backend": "auto",
"recommendedModel": "Auto",
"keywords": [
"search", "grep", "find", "explain", "read", "docs",
"rename", "boilerplate", "simple", "small", "single-file"
]
},
"fleet": {
"backend": "openclaw",
"recommendedModel": "qwen2.5-7b",
"keywords": [
"multi-file", "tests", "refactor", "implement", "migration",
"pattern", "transform", "integration", "batch", "known"
]
},
"premium": {
"backend": "sonnet",
"recommendedModel": "Claude Sonnet 4.6",
"keywords": [
"architecture", "ambiguous", "complex", "hard", "risk",
"security", "performance", "concurrency", "incident", "design"
]
}
},
"escalation": {
"premiumOn": ["failed", "stuck", "unclear", "cross-system", "trade-off"],
"fleetOn": ["medium", "repeated", "workflow", "generate", "coverage"]
}
}
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.
- 5d ago First seen · 81 lines · 0 tokens per session scan A 6abc47625fd0
router-policy is an agent published in the GitHub repository chf3198/copilot-governance (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 695 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.