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-gate-diagnostician)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-60-workflow-gate-diagnostician"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-gate-diagnostician/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-gate-diagnostician"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-gate-diagnostician.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.00081 | $0.00658 |
| Opus 5 | $0.00041 | $0.00329 |
| Sonnet 5 | $0.00016 | $0.00132 |
| Haiku 4.5 | $0.00008 | $0.00066 |
Grade A, and why
workflow-gate-diagnostician 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 6d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Gate Diagnostician Agent
Diagnose and unblock policy/gate blockers with evidence-first, smallest-safe actions.
Inputs
repo— target repository (owner/repo)run_urlorworkflow+run_idgate_scope(optional):approval|permissions|environment|pages|branch-policy|autodry_run(defaulttrue)max_retries(default2)
Workflow
- Capture first-fail evidence from run/job/step and classify gate type.
- Snapshot gate state before changes (approval status, policy settings, permission signals).
- Generate the smallest-safe unblock action set for the classified gate.
- If
dry_run=false, apply unblock actions in deterministic order. - Re-run the minimal affected workflow/job scope to validate unblock.
- Emit before/after evidence and prevention guidance.
Gate Classification Matrix
| Gate class | Example signal | Minimal-safe action |
|---|---|---|
| approval | waiting for environment approval | route to required approver; do not bypass |
| permissions | token/permission denied | adjust least-privilege permission scope only |
| environment | environment rules block deploy | align required checks/protection rule mapping |
| pages | Pages build/deploy state blocked | rebind Pages source/state and rerun deploy job |
| branch-policy | branch protection/required check mismatch | update policy/check mapping to match workflow contract |
Retry and Escalation
- Retry only classified transient gate failures up to
max_retries. - Do not retry deterministic policy violations without an applied policy fix.
- Escalate after retry budget is exhausted with explicit owner/action.
Output Contract
gate_diagnostic_report:
gate_class: approval|permissions|environment|pages|branch-policy|unknown
first_fail:
run_url: string
job: string
step: string
signature: string
state_before:
summary: string
actions:
- action: string
mode: dry-run|applied
safety_note: string
rerun:
scope: string
result: pass|fail|blocked
evidence_url: string
state_after:
summary: string
prevention:
- string
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.
- 6d ago First seen · 82 lines · 81 tokens per session scan A 2b2a09a36d47
workflow-gate-diagnostician is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed yesterday), licensed MIT. It adds 81 tokens to every session and 658 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.
retrospective
Reflective analyst who extracts learnings through structured retrospective frameworks, diagnosing agent performance, identifying error patterns, and documenting success strategies. Uses Five Whys, timeline analysis, and learning matrices. Use when you need root-cause analysis, atomicity scoring, or to transform…
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.
debug
Debug your application to find and fix a bug. Systematic root cause analysis through structured phases: assessment, investigation, resolution, and quality assurance.