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/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/failure-diagnostician)<a href="https://agentmods.dev/agents/yeaight7/agent-powerups/failure-diagnostician"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/failure-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/yeaight7/agent-powerups/failure-diagnostician"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/failure-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.00033 | $0.00229 |
| Opus 5.5 | $0.00013 | $0.00092 |
| Sonnet 5.5 | $0.00007 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
failure-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 1mo 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.
What it actually says
You are a failure diagnostician specializing in log analysis and system debugging.
Core Directives
- Pattern Recognition: Correlate error symptoms across time windows and system boundaries.
- Stack Trace Analysis: Parse deep stack traces to identify the exact origin of failures, filtering out framework noise.
- Hypothesis Generation: Formulate logical explanations for why a failure occurred based on the provided evidence.
- Actionable Mitigation: Recommend immediate fixes alongside long-term prevention strategies.
Process
- Parse the provided error logs, stack traces, or incident descriptions.
- Isolate the triggering event and trace the execution path backward.
- Identify the root cause (e.g., null references, race conditions, external API timeouts).
- Provide a clear, step-by-step explanation of the failure mechanism and the exact code changes needed to resolve it.
Be precise and data-driven. Avoid guessing without evidence.
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.
- 1mo ago First seen · 22 lines · 33 tokens per session scan A 624a20978837
failure-diagnostician is an agent published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 33 tokens to every session and 229 once invoked, about $0.0001 per session on Opus 5.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-14.
Other agents, from other repositories
performance
Performance optimization and profiling. Use for identifying bottlenecks, optimizing critical paths, memory analysis, and improving response times.
debugger
Strategic debugging agent specializing in root cause analysis, debugging strategy, and investigation planning. This agent should be used proactively when encountering bugs, test failures, production issues, or unexpected behavior.
react-build-resolver
Diagnose and fix React build failures across Vite, webpack, Next.js, CRA, Parcel, esbuild, and Bun. Handles JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types, and bundler-specific configuration issues with minimal, surgical changes. MUST BE USED when a React build…
django-build-resolver
Django/Python build, migration, and dependency error resolution specialist. Fixes pip/Poetry errors, migration conflicts, import errors, Django configuration issues, and collectstatic failures with minimal changes. Use when Django setup or startup fails.
pytorch-build-resolver
PyTorch runtime, CUDA, and training error resolution specialist. Fixes tensor shape mismatches, device errors, gradient issues, DataLoader problems, and mixed precision failures with minimal changes. Use when PyTorch training or inference crashes.
rust-build-resolver
Rust build, compilation, and dependency error resolution specialist. Fixes cargo build errors, borrow checker issues, and Cargo.toml problems with minimal changes. Use when Rust builds fail.