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-ci-failure-escalation)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-60-workflow-ci-failure-escalation"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-ci-failure-escalation/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-ci-failure-escalation"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-ci-failure-escalation.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.00079 | $0.00704 |
| Opus 5 | $0.00039 | $0.00352 |
| Sonnet 5 | $0.00016 | $0.00141 |
| Haiku 4.5 | $0.00008 | $0.00070 |
Grade A, and why
ci-failure-escalation 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 4d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Failure Escalation Agent
Purpose: Monitors a GitHub Actions workflow job for consecutive failures, halts the line by opening a blocking issue and gating deployments past the configured threshold — the andon cord pattern. Complements self-healing-ci (automated remediation); this agent escalates when remediation isn't working.
Inputs
repo(required) — GitHub owner/repo slugworkflow_name(required) — workflow file/display namejob_name(required) — job within the workflow to monitorfailure_threshold(optional, default3) — consecutive failures before escalatingenvironment(optional) — deployment environment to gate
Workflow
- Query recent runs — fetch the last
failure_threshold + 2runs ofworkflow_name, filter tojob_name. Consultdocs/reference/repo-pathways.mdfor a matching signature before opening a new blocking issue. - Count consecutive failures — walk runs newest→oldest; stop at first success/skip.
- If consecutive failures ≥ threshold:
a. Open or update a blocking issue keyed by a stable
repo/workflow_name/job_namemarker (not the failure count, so repeated failures update the issue instead of duplicating), labelblocker, body with failure timeline, last error snippet, remediation — see template in detail file. b. Gate the environment (if provided): confirmcustom_branch_policies: truefirst (only that mode can be halted); snapshot each policy's id/name/type; require explicit Tier-3 confirmation restating target/impact before deleting them (docs/reference/guardrails/tool-confirmation-policy.md); otherwise post manual gate instructions. c. Post a new failing check run referencing the halt (if permitted) linking the blocking issue. - Below threshold: report count/margin; suggest
self-healing-cifirst for App Service/startup failures. - On resolution — comment with summary, recreate the snapshotted policies (name/type; ids are new), confirm next run passes.
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.
- 4d ago Changed d5c3b71c61bf
- 6d ago First seen · 43 lines · 79 tokens per session scan A ed221898788f
ci-failure-escalation is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 704 once invoked, about $0.0004 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
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
meeting-organizer
Prepare and summarize meeting docs.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.