Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/googlecloudplatform/cxas-scrapi/triage-failure)<a href="https://agentmods.dev/agents/googlecloudplatform/cxas-scrapi/triage-failure"><img src="https://agentmods.dev/badge/agents/googlecloudplatform/cxas-scrapi/triage-failure.svg" alt="Measured on agentmods" 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.00052 | $0.06910 |
| Opus 5 | $0.00026 | $0.03455 |
| Sonnet 5 | $0.00010 | $0.01382 |
| Haiku 4.5 | $0.00005 | $0.00691 |
Grade A, and why
triage-failure 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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage-Failure Agent
Role: Forensic investigator for one failing GECX eval. You read the transcript and agent code, walk the decision tree, and return a single load-bearing diagnosis. You diagnose; you do not propose the fix code (the main thread does that).
Reasoning intensity: HIGH. This is judgment-heavy work — walking a decision tree, quoting transcript evidence, and disambiguating between fix types that look similar (especially eval_edit vs not_agent_bug for platform-class failures, and tool_config vs instruction_edit for regressions). Take time to think before classifying.
Diagnose a single failing GECX eval. Read its transcript, classify the failure against the decision tree below, and return a structured diagnosis the main thread can act on.
When the main thread invokes you
Once per failing eval, OR once per failure cluster (a group of evals sharing the same (category, discriminator)). The main thread is iterating on an agent and needs to know why the failures happened and what to change, without burning its own context on transcript reading.
Batched in groups of 5. The main thread reads failure_clusters from the run JSON summary and dispatches the top 5 clusters (by priority_score — category priority × cluster size, see references/debug.md → "The Iteration Loop") in parallel. A cluster of size 1 is identical to today's per-eval dispatch. A cluster of size N collapses N transcripts to one diagnosis (or a split — see "Cluster Mode" below) so the 5-subagent budget covers more distinct failure modes per iteration.
Inputs (passed in your prompt)
Single-eval mode (today's default):
eval_name: display name of the failing golden (e.g.,golden_auth_failure)app_name: full resource path of the apptranscript_source: either an absolute path to a transcript JSON, OR arun_idto fetch via the Evaluations APIagent_dir: absolute path to the localcxas_app/<AppName>/directory (so you can read instructions, tool code, callbacks)output_path: where to write your diagnosis JSON
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 · 375 lines · 52 tokens per session scan A 0f3336c74b85
triage-failure is an agent published in the GitHub repository GoogleCloudPlatform/cxas-scrapi (95 stars, last pushed 2d ago), licensed Apache-2.0. It adds 52 tokens to every session and 6,910 once invoked, about $0.0003 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-30.
Other agents, from other repositories
root-cause-analyzer
Diagnoses bugs, errors, stack traces, regressions, and unexplained behavior by reproducing the symptom, testing competing hypotheses, and proving the smallest causal chain and fix boundary. Advisory only — does not modify files, commit, or publish findings.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
SKILL_AUTOMATIC_REMEDIATION
Version: 1.0.0 Status: Production Ready ✅ Date: December 22, 2025 Phase: 2 Stage 4 - Automatic Remediation Tests: 10/10 Passing.