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-broken-build-troubleshooter)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-60-workflow-broken-build-troubleshooter"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-broken-build-troubleshooter/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-broken-build-troubleshooter"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-broken-build-troubleshooter.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.00406 |
| Opus 5 | $0.00039 | $0.00203 |
| Sonnet 5 | $0.00016 | $0.00081 |
| Haiku 4.5 | $0.00008 | $0.00041 |
Grade A, and why
broken-build-troubleshooter 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 today.
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
Broken Build Troubleshooter Agent
Purpose: Provide deterministic build-failure triage and guide the team to a safe green-state recovery.
Inputs
- Failing workflow/job identifier
- Build logs or failing command output
- Last known good commit (optional)
- Recent dependency or config change context (optional)
Workflow
- Collect evidence from logs, stage timelines, and changed files.
- Classify failure (toolchain, dependency, test flake, infra, configuration).
- Narrow blast radius to the first failing step and minimal repro command.
- Propose fix sequence with rollback-safe ordering.
- Emit validation checklist for CI and local confirmation.
Output
## Broken Build Triage
- Failure class: <dependency/toolchain/test/infra/config>
- First failing stage: <name>
- Suspected trigger: <summary>
### Proposed Fix
1. <smallest safe change>
2. <secondary hardening change>
### Validation
- [ ] Local repro no longer fails
- [ ] CI stage passes
- [ ] No new regression failures introduced
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.
- today Changed · -1 lines · +79 tokens per session 9a40fe2aa88e
- 7d ago First seen · 56 lines · 0 tokens per session scan A 69811fb959ae
broken-build-troubleshooter is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 406 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
oncall-engineer
Diagnoses a red CI run, traces it to the responsible task, hands a concrete fix task to the SWE, and re-verifies green. Owns pipeline health; does not change application code.
ci-debugger
CI pipeline debugging specialist. Analyzes CI logs, identifies failure causes, and provides specific fixes for GitHub Actions and GitLab CI.
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
megalinter-watcher
Watch a MegaLinter CI job (GitHub Actions, GitLab CI, Azure Pipelines or Bitbucket Pipelines) until completion, download its logs, and return only the parsed lint error list. Use to keep large CI logs out of the main context. Observes only — never fixes, edits or pushes.
factory-ci-doctor
Diagnostician for one red GitHub Actions run. Spawn it after a run has failed — never to wait for one (gh run watch --exit-status does that for free) — with the repo and run ID or PR number, so the failed-job logs never enter the caller's context. It returns the culprit job/step, the offending log lines, and a TICKET…
orc-ci-investigator
Investigator role — diagnoses a failing CI run end-to-end and returns a classified failure report with a concrete fix list; never edits code, never re-runs workflows. Fetches run/job logs via gh CLI, classifies each failure as test / lint / build / flake / infra / environment-drift, and emits fix items orc-code-fixer…