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-60-workflow-incident-to-backlog-router)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-60-workflow-incident-to-backlog-router"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-incident-to-backlog-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-60-workflow-incident-to-backlog-router"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-incident-to-backlog-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.00113 | $0.00622 |
| Opus 5 | $0.00056 | $0.00311 |
| Sonnet 5 | $0.00023 | $0.00124 |
| Haiku 4.5 | $0.00011 | $0.00062 |
Grade A, and why
incident-to-backlog-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 8d 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
Incident-to-Backlog Router Agent
Routes incident signals into prioritized backlog items with required portfolio fields pre-populated and closure linkage tracked.
Inputs
incident_id,severity(SEV1-SEV5),title,description(required)affected_service,sre_impact,security_involved,repo,sprint,dry_run,create,check_orphans(optional)
Workflow
- Detect duplicate open issues (>80% keyword overlap); classify type (bug/enhancement/security/chore).
- Populate portfolio fields: Type, Priority, Risk, Guardrail State, SRE Impact, Wave.
- If
createis true, create or update the remediation GitHub issue with pre-filled fields and SLA target; otherwise return a routing preview only. - Route to correct queue: SEV1/2 to current sprint, SEV3 to next sprint/maintenance, SEV4 to maintenance queue, SEV5 to backlog.
- Post closure linkage comment on the originating incident only when issue creation is enabled.
- Detect orphaned incidents (
--check-orphans): warn, then auto-create after 24-hour grace period whencreateis enabled. - Log routing decision via
decision-log-captureskill.
Output
Routing decision result: status (ROUTED/DUPLICATE/ORPHAN_DETECTED/DRY_RUN), remediation issue number and URL (when created), portfolio fields, SLA targets, closure linkage, and routing decision log reference.
References
Routing policy tables, SLA targets, portfolio field derivation, issue body template, queue commands, orphan detection query, output YAML schema: agents/references/incident-to-backlog-router-detail.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.
- 8d ago First seen · 50 lines · 113 tokens per session scan A 679014e93f0f
incident-to-backlog-router is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed yesterday), licensed MIT. It adds 113 tokens to every session and 622 once invoked, about $0.0006 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 agents, from other repositories
ijfw-debug-session-manager
Use when managing a multi-cycle debug session that needs checkpoint/continuation across context resets.
incident-responder
Production incident response agent'i. Severity classification (P0-P3), runbook execution, root cause analysis, impact assessment, communication template'leri, post-incident review ve remediation tracking.
Compliance Auditor
Perform non-destructive cross-artifact consistency and quality analysis across spec, plan, and tasks.
linear-ticket-investigator
Extract evidence from a single Linear ticket — read the ticket, locate affected code, and return an Evidence Record matching the /fix-bug Phase 2 schema. Returns structured evidence only — no root-cause analysis, no fix proposal, no confidence scoring (those are /fix-bug's job via holistic-analysis). Used by…
evolve-scout-scan
MAP-step slice scanner for the scout map-reduce decomposition. Scans ONE codebase slice (a package group) and emits a structured ScanDigest. Does NOT select tasks or write evals — the scout synthesizer (REDUCE) does that from the merged digests.
jira-ops
Inspect JIRA-side cache + project context discovery via the jira-as CLI wrapper. Diagnostic surface: cache-status, cache-clear, discover-project. Routed by mk:jira-ops skill. NOT for issue CRUD; NOT for project admin (jira-admin).