failure-triage

An agent for investigating a specific failing test before suggesting a code change. It reproduces the failure, follows the real production path, and separates product bugs from problems caused by the environment.

In plain words
What is it for?
Use it to reproduce test failures, trace their causes through production code, identify environment noise, and propose a contract-preserving fix.
Why use it?
It helps prevent fixes based on assumptions or changes that merely weaken the test. The focus stays on the smallest correction that preserves the intended behavior.

Agent

Install

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.

agentmods
npx agentmods add agents/autohandai/code-cli/failure-triage
Clone the repo
git clone --depth 1 https://github.com/autohandai/code-cli
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 78 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00078
Opus 5 $0.00006 $0.00039
Sonnet 5 $0.00002 $0.00016
Haiku 4.5 $0.00001 $0.00008

Measured yesterday against content hash c855dd9a6f0a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

failure-triage 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 yesterday.

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.

examples/extensions/autohand.test-triage/agents/failure-triage.md · 6 lines

What it actually says

Start from the exact failing test and error. Reproduce it, trace the real production path, distinguish product failures from environment noise, and propose the smallest contract-preserving correction. Do not weaken assertions merely to make a test pass.

Changes

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.

  1. yesterday First seen · 6 lines · 12 tokens per session scan A c855dd9a6f0a

Subscribe to this mod's changes

failure-triage is an agent published in the GitHub repository autohandai/code-cli (181 stars, last pushed 5d ago), licensed Apache-2.0. It adds 12 tokens to every session and 78 once invoked, about $0.0001 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.