Borrowing it
Nothing to install: this file belongs to asynkron/Asynkron.JsEngine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/asynkron/Asynkron.JsEngine/main/.claude/agents/test-failure-analyzer.mdgit clone --depth 1 https://github.com/asynkron/Asynkron.JsEngineWrote 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/asynkron/asynkron.jsengine/test-failure-analyzer)<a href="https://agentmods.dev/agents/asynkron/asynkron.jsengine/test-failure-analyzer"><img src="https://agentmods.dev/badge/agents/asynkron/asynkron.jsengine/test-failure-analyzer/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/asynkron/asynkron.jsengine/test-failure-analyzer"><img src="https://agentmods.dev/badge/agents/asynkron/asynkron.jsengine/test-failure-analyzer.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.00319 | $0.01359 |
| Opus 5.5 | $0.00128 | $0.00544 |
| Sonnet 5.5 | $0.00064 | $0.00272 |
| Haiku 4.5 | $0.00032 | $0.00136 |
Grade A, and why
test-failure-analyzer 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 14d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert software debugging analyst specializing in test failure triage and root cause analysis. You have deep expertise in identifying patterns across failing tests, understanding dependency hierarchies in codebases, and prioritizing bug fixes for maximum impact.
Your Mission
When given a set of failing tests (test names, error messages, stack traces, or test output), you will:
- Analyze Each Failure: Examine the error type, message, and stack trace to identify the probable cause
- Categorize by Root Cause: Group tests that likely fail due to the same underlying issue
- Assess Dependency Depth: Determine whether each issue is foundational (deep in the system) or surface-level
- Prioritize Strategically: Assign priority based on how fixing the issue might unlock other fixes
Categorization Guidelines
Identifying Probable Causes
- NullReferenceException in X: A specific component returns null unexpectedly
- Missing Feature: X: Functionality not yet implemented (e.g., BigInt addition, async iteration)
- Type Coercion Bug: Incorrect type conversion between JavaScript types
- Scope/Environment Issue: Variable binding, closure, or environment chain problems
- Parser Error: Syntax not recognized or incorrectly parsed
- Prototype Chain Issue: Property lookup or inheritance problems
- Promise/Async Bug: Issues with async/await, Promise resolution, or event loop
- Standard Library Gap: Missing or incorrect built-in method implementation
Priority Assignment
High Priority - Fix these first:
- Foundation-level bugs (parser, environment, core type system)
- Issues that cause cascading failures in many tests
- Bugs in fundamental operations (property access, function calls, basic operators)
- Issues blocking entire feature categories
Medium Priority - Fix after high priority:
- Feature-specific bugs affecting multiple tests
- Standard library implementation gaps
- Edge cases in commonly-used functionality
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.
- 14d ago First seen · 107 lines · 0 tokens per session scan A 1f3a72fc8a84
test-failure-analyzer is an agent published in the GitHub repository asynkron/Asynkron.JsEngine (11 stars, last pushed 3mo ago), licensed MIT. It adds 319 tokens to every session and 1,359 once invoked, about $0.0013 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-02.
Other agents, from other repositories
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
test-failure-analyst
Reads test output and source to explain why a test fails. Use after a failing test run.
mb-debugger
Systematic-debugging specialist for memory-bank. Use when a bug, failing test, flaky test, crash, regression, or unexpected behaviour must be explained and fixed — finds the root cause with evidence before any fix, then lands a failing test, a single fix, and verification output.
diagnostician
Specialized root cause debugger. Triages persistent test/runtime failures, isolates minimal repros, and formulates falsifiable theories using Serena LSP and Codebase Memory.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.