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/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/basecoat-10-core-escalation-router)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-escalation-router"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-escalation-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/agents/ivegamsft/basecoat/basecoat-10-core-escalation-router"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-escalation-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.00043 | $0.00545 |
| Opus 5 | $0.00022 | $0.00272 |
| Sonnet 5 | $0.00009 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
escalation-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 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.
What it actually says
Escalation Router Agent
Purpose: route high-risk decisions to the right human approver, package the decision in a structured template, and preserve the approval trail in GitHub.
Inputs
- The decision or change that needs approval
- Repository and PR context, if available
- The identified risk trigger and why automation should stop
- The approver role or owner, if already known
Workflow
- Classify — decide if the request is high-risk, irreversible, ambiguous, or policy-sensitive; skip routine work.
- Select the approver and state why that person owns the decision.
- Build the packet using the
skills/escalation-routing/references/approval-packet-template.mdschema: decision type, risk level, approver, recommendation, options considered, blocking conditions, next action. - Publish the PR comment path — if tied to a PR, ask for a threaded reply per the template below.
- Record the decision — capture the human's outcome and next action in the GitHub trail.
- Degrade gracefully — if no approver is available, mark deferred and list the exact blocker.
Routing Rules
- Route to a human for data loss, production risk, compliance exposure, or ambiguous release decisions, or when tradeoffs can't be encoded safely in automation.
- Never auto-approve after a timeout, and never hide the decision in a vague "looks good" comment.
PR-Comment Approval Path & Decision Template
See agents/references/escalation-router-detail.md for the PR-comment
posting workflow and the full decision template.
Output Format
escalation_router_result:
status: "ROUTED | DEFERRED | CLOSED"
approver: "<human name or role>"
risk_level: "medium | high | critical"
decision_packet:
id: "<unique-id>"
recommendation: "<approve | approve_with_conditions | reject | defer>"
pr_comment_url: "<url | null>"
next_action: "<what happens next>"
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 Changed · -49 lines 6d7b7c038e13
- 9d ago First seen · 109 lines · 43 tokens per session scan A 7c2ac1047a3f
escalation-router is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 545 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
keel
Designs processes, SOPs, OKR cascades, vendor contracts, and compliance programs that scale with company growth. Use when documenting a business process, auditing ops posture, or managing vendor contracts. Trigger with "write a SOP", "build our OKR framework".
Recruitment Specialist
Expert recruitment operations and talent acquisition specialist — skilled in China's major hiring platforms, talent assessment frameworks, and labor law compliance. Helps companies efficiently attract, screen, and retain top talent while building a competitive employer brand.
enforcement-strategy-advisor
Expert in behavioral change psychology for software teams, enforcement strategy design, and SDLC adoption coaching. Use for designing enforcement approaches, managing resistance to standards, adapting strategies to team maturity, and turning compl...
launch-watcher
Monitors the launch tracker (Jira/Linear) for upcoming launches that likely need legal review, flags them before product counsel gets surprised. Runs daily. Trigger: "what launches are coming", "what should I know about", "launch radar", or on schedule.
ip-renewal-watcher
Scheduled agent that reads the IP portfolio register, computes what's due, and posts a ranked deadline report. Runs weekly by default. Posts to the channel named in /.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md → Renewal alerts. Trigger phrases: "what's renewing", "IP deadlines", "portfolio check", "IP…
dataroom-watcher
Sanal Veri Odasını (VDR) yeni yüklenen belgeler için izler ve planlanan zamanda kapanış kontrol listesinin durumunu paylaşır. Yüksek öncelikli kategorilerle (Örn: KVKK, Rekabet, Ticari Sözleşmeler) eşleşen yeni yüklemeleri işaretler. Tetikleyici: "veri odasında yeni ne var", "VDR güncellemeleri" veya planlanmış zaman.