Borrowing it
Nothing to install: this file belongs to Eduardo-Salvador/Agent-Harness-Kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Eduardo-Salvador/Agent-Harness-Kit/main/.agents/skills/request-router/SKILL.mdgit clone --depth 1 https://github.com/Eduardo-Salvador/Agent-Harness-KitWrote 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/skills/eduardo-salvador/agent-harness-kit/request-router)<a href="https://agentmods.dev/skills/eduardo-salvador/agent-harness-kit/request-router"><img src="https://agentmods.dev/badge/skills/eduardo-salvador/agent-harness-kit/request-router/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/skills/eduardo-salvador/agent-harness-kit/request-router"><img src="https://agentmods.dev/badge/skills/eduardo-salvador/agent-harness-kit/request-router.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.00035 | $0.00294 |
| Opus 5.5 | $0.00014 | $0.00118 |
| Sonnet 5.5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
request-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 1mo 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
Request router
- Before mutating work or Harness ceremony, read
../../../harness/playbooks/request-routing.mdand../../../docs/ADAPTIVE-EXECUTION.md. Read-only audit/diagnosis does not trigger first-run. - Explicit full wins. Otherwise use full for two or more real agents, a human loop, required audit, insufficient model capability, or unresolved consequential ambiguity. Actual security/privacy/authorization/destructive changes require full audit; API/dependency keywords alone are not triggers.
- Classify deterministically first. Use an available economical AI classifier only when ambiguity remains and classification is cheaper than the work. Do not call a separate provider, invent credentials, hardcode a model ID, or claim a silent model switch.
- Route to exactly one lane and independently assign
assurance: none|light|full. Unresolved consequential ambiguity selectsfull-harness; ordinary uncertainty may be resolved by bounded inspection. - For
vibe, permit a small local behavior change in one workstream with no Harness artifacts or mandatory RED, but require a focused deterministic check. - Re-evaluate scope before further edits. Failed verification starts bounded in-scope recovery; promote only when a full-Harness condition is discovered.
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.
- 1mo ago Changed 67c7fe5474ac
- 1mo ago First seen · 14 lines · 35 tokens per session scan A 8937a0ad86d1
request-router is a skill published in the GitHub repository Eduardo-Salvador/Agent-Harness-Kit (6 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 294 once invoked, about $0.0001 per session on Opus 5.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-08-31.
Other skills, from other repositories
forming-an-openrig-mental-model
Use when the system around you does not make sense yet: you just booted into a seat and do not know how the pieces fit; someone said rig, pod, seat, fleet, topology, or slice and you are not certain what they mean here; you are unsure what kind of rig you are in or what it is for; you do not know how skills reach you…
orienting-to-an-inherited-seat
Use when you have just been primed into an EXISTING seat through a planned handover — a different agent retired and handed you the seat plus its earned context — and you need a world model of what just happened to you. Covers how a handover differs from compaction and from a fresh launch, the…
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a…
applying-a-permission-policy
Use before launching a team during agent-guided setup, or when a user asks to configure OpenRig command permissions, reduce repeated native approval prompts, or apply a selected rig/seat permission policy.
messaging-the-human
Use when project policy calls for a human decision or update, a human delivery is pending or failed, or a reply must resume the right work.
openrig-upgrade
Use when an agent is preparing or performing an OpenRig CLI/daemon upgrade and must preserve live seats, verify each mutation, or reconcile managed plugin and skill files without overwriting local work.