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/commands/yeaight7/agent-powerups/diagnose-failure)<a href="https://agentmods.dev/commands/yeaight7/agent-powerups/diagnose-failure"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/diagnose-failure/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/commands/yeaight7/agent-powerups/diagnose-failure"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/diagnose-failure.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.00023 | $0.00216 |
| Opus 5.5 | $0.00009 | $0.00086 |
| Sonnet 5.5 | $0.00005 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
diagnose-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 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
Diagnose Failure
You are an expert in debugging and failure analysis. Your task is to investigate the provided error context, find the root cause, and provide a concrete resolution.
Context
$ARGUMENTS
Diagnostic Steps
- Analyze Symptoms: Review the provided logs, stack traces, or unexpected outputs.
- Trace Execution: Reconstruct the likely execution path that led to the invalid state.
- Identify Root Cause: Pinpoint the exact line of code, missing configuration, or external dependency failure responsible.
- Formulate Solution: Provide the exact code or configuration changes required to fix the issue.
- Prevention: Briefly suggest how to prevent similar errors in the future (e.g., adding an assertion, improving a type definition, or updating an error boundary).
Be concise and focus on actionable solutions. Do not generate generic debugging advice; tailor your response to the exact failure provided.
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 · 23 tokens per session scan A 95961984cfa8
diagnose-failure is a command published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 23 tokens to every session and 216 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 commands, from other repositories
t800-fix
A command for making a narrow, predefined fix to existing agents, skills, commands, rules, or hooks. A fix-pack is a file listing the exact changes to make.
t800-doctor
A command that runs a scripts-only health report for a T-800 or target plugin setup. It reports the version, profile, memory location, state, item counts, always-applied items, and recent audits.
t-800-factory-validate
A validation command for T-800 Factory files. It runs checks on agents and examines the graph of how those agents connect.
debug-trace
Analyze error and trace execution path to identify root cause.
cpp-build
Fix C++ build errors, CMake issues, and linker problems incrementally. Invokes the cpp-build-resolver agent for minimal, surgical fixes.
go-build
Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent for minimal, surgical fixes.