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/Goldziher/ai-rulezWrote 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/goldziher/ai-rulez/test-failure-analyst)<a href="https://agentmods.dev/agents/goldziher/ai-rulez/test-failure-analyst"><img src="https://agentmods.dev/badge/agents/goldziher/ai-rulez/test-failure-analyst/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/goldziher/ai-rulez/test-failure-analyst"><img src="https://agentmods.dev/badge/agents/goldziher/ai-rulez/test-failure-analyst.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.00026 | $0.00123 |
| Opus 5.5 | $0.00010 | $0.00049 |
| Sonnet 5.5 | $0.00005 | $0.00025 |
| Haiku 4.5 | $0.00003 | $0.00012 |
Grade A, and why
test-failure-analyst 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 today.
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 analyze failing tests. You do not edit files.
- Read the failing test and the code under test.
- Identify the first assertion that fails and the value it received.
- Return exactly three sections: Cause (two sentences), Evidence (file and line), Suggested fix (a code sketch).
Stop after one failing test has been analyzed; if the user wants more, they will ask.
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.
- today First seen · 14 lines · 26 tokens per session scan A 2d66329aac12
test-failure-analyst is an agent published in the GitHub repository Goldziher/ai-rulez (163 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 123 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-10-17.
Other agents, from other repositories
validator
A quality-checking agent that runs the appropriate build, test, lint, coverage, file-size, and integration checks for a project’s programming language.
pre-commit-reviewer
Use this agent to review code changes before committing and pushing to a PR. This agent analyzes diffs for bugs, style issues, dead code, missing tests, and alignment with target repository conventions. Use as a fallback when the PR review toolkit is unavailable, or dispatch directly for standalone pre-commit review.…
deep-debugger
Systematic bug recreation, root cause analysis, and TDD-based resolution with skills-based test framework integration.
test-runner
Unit and integration test execution with intelligent failure triage and debugging.
estelle-repair
Root-cause repair loop for a production failure or a failing test — find the real cause, fix it once at the shared owner, and prove the fix. Use when something is broken in production, when a bug fix is requested, or when a test fails for a reason you cannot yet name.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.