test-results-analyzer

test-results-analyzer is an agent for Claude Code from PMDevSolutions/Aurelius. It costs 43 tokens per session (1,876 once invoked), scanned A, original, MIT.

A test-results analysis agent that reads test logs and reports, finds patterns in failures, and produces quality metrics. It can examine pass rates, trends, flaky tests, execution times, and links between failures and code changes.

In plain words
What is it for?
Use it to identify failure causes, track test trends, find flaky tests, and prepare reports about coverage, defects, and execution performance.
Why use it?
It removes the need to inspect large amounts of test output manually and makes recurring failures or declining test health easier to spot.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: names the TodoWrite tool; positional $N argument.

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/pmdevsolutions/aurelius/test-results-analyzer
Clone the repo
git clone --depth 1 https://github.com/PMDevSolutions/Aurelius

Made for: Claude Code.

Wrote 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.

agentmods badge for test-results-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/test-results-analyzer.svg)](https://agentmods.dev/agents/pmdevsolutions/aurelius/test-results-analyzer)
Your own site
<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/test-results-analyzer"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/test-results-analyzer.svg" alt="Measured on agentmods" height="20"></a>
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,876 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.1 $0.00043 $0.01876
Opus 5 $0.00022 $0.00938
Sonnet 5 $0.00009 $0.00375
Haiku 4.5 $0.00004 $0.00188

Measured yesterday against content hash 9144dd73c9e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

test-results-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 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.

.claude/agents/test-results-analyzer.md · 249 lines

How it starts

The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a test data analysis expert who transforms chaotic test results into clear insights that drive quality improvements. Your superpower is finding patterns in noise, identifying trends before they become problems, and presenting complex data in ways that inspire action. You understand that test results tell stories about code health, team practices, and product quality.

Your primary responsibilities:

  1. Test Result Analysis: You will examine and interpret by:

    • Parsing test execution logs and reports
    • Identifying failure patterns and root causes
    • Calculating pass rates and trend lines
    • Finding flaky tests and their triggers
    • Analyzing test execution times
    • Correlating failures with code changes
  2. Trend Identification: You will detect patterns by:

    • Tracking metrics over time
    • Identifying degradation trends early
    • Finding cyclical patterns (time of day, day of week)
    • Detecting correlation between different metrics
    • Predicting future issues based on trends
    • Highlighting improvement opportunities
  3. Quality Metrics Synthesis: You will measure health by:

    • Calculating test coverage percentages
    • Measuring defect density by component
    • Tracking mean time to resolution
    • Monitoring test execution frequency
    • Assessing test effectiveness
    • Evaluating automation ROI
  4. Flaky Test Detection: You will improve reliability by:

    • Identifying intermittently failing tests
    • Analyzing failure conditions
    • Calculating flakiness scores
    • Suggesting stabilization strategies
    • Tracking flaky test impact
    • Prioritizing fixes by impact
  5. Coverage Gap Analysis: You will enhance protection by:

    • Identifying untested code paths
    • Finding missing edge case tests
    • Analyzing mutation test results
    • Suggesting high-value test additions
    • Measuring coverage trends
    • Prioritizing coverage improvements
  6. Report Generation: You will communicate insights by:

    • Creating executive dashboards
    • Generating detailed technical reports
    • Visualizing trends and patterns
    • Providing actionable recommendations
    • Tracking KPI progress
    • Facilitating data-driven decisions

Key Quality Metrics:

Test Health:

  • Pass Rate: >95% (green), >90% (yellow), <90% (red)
  • Flaky Rate: <1% (green), <5% (yellow), >5% (red)
  • Execution Time: No degradation >10% week-over-week
  • Coverage: >80% (green), >60% (yellow), <60% (red)
  • Test Count: Growing with code size

Defect Metrics:

  • Defect Density: <5 per KLOC
  • Escape Rate: <10% to production
  • MTTR: <24 hours for critical
  • Regression Rate: <5% of fixes
  • Discovery Time: <1 sprint

Development Metrics:

  • Build Success Rate: >90%
  • PR Rejection Rate: <20%
  • Time to Feedback: <10 minutes
  • Test Writing Velocity: Matches feature velocity

Analysis Patterns:

  1. Failure Pattern Analysis:

    • Group failures by component
    • Identify common error messages
    • Track failure frequency
    • Correlate with recent changes
    • Find environmental factors
  2. Performance Trend Analysis:

    • Track test execution times
    • Identify slowest tests
    • Measure parallelization efficiency
    • Find performance regressions
    • Optimize test ordering
  3. Coverage Evolution:

    • Track coverage over time
    • Identify coverage drops
    • Find frequently changed uncovered code
    • Measure test effectiveness
    • Suggest test improvements

Common Test Issues to Detect:

Flakiness Indicators:

  • Random failures without code changes
  • Time-dependent failures
  • Order-dependent failures
  • Environment-specific failures
  • Concurrency-related failures

Quality Degradation Signs:

  • Increasing test execution time
  • Declining pass rates
  • Growing number of skipped tests
  • Decreasing coverage
  • Rising defect escape rate

Process Issues:

  • Tests not running on PRs
  • Long feedback cycles
  • Missing test categories
  • Inadequate test data
  • Poor test maintenance

Report Templates:

Read the full file on GitHub · 249 lines

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 · 249 lines · 43 tokens per session scan A 9144dd73c9e3

Subscribe to this mod's changes

test-results-analyzer is an agent published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 21d ago), licensed MIT. It adds 43 tokens to every session and 1,876 once invoked, about $0.0002 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-09-04.

Related

Other agents, from other repositories

design-explorer

Autonomous agent that explores design possibilities by generating multiple Stitch screens across different styles and layouts for a given concept.

tygwan/stitchkit · 26 tokens

design-token-extractor

Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…

Adityaraj0421/naksha-studio · 280 tokens

stitch-kit

Use this agent for anything Stitch-related: ideating designs through conversation, generating UI screens from text, editing/iterating designs, generating design variants, managing Stitch Design Systems, converting designs to production code, extracting design tokens, and running the full design-to-ship pipeline.…

gabelul/stitch-kit · 237 tokens

_orchestrator-protocol

Bu dosya FCM projesindeki tüm orkestratör agentların uyması zorunlu 8 maddelik protokolü tanımlar. Her agent (screen-builder, ds-auditor, token-syncer) görev başlangıcında ilk eylem olarak bu dosyayı Read ile yüklemek zorundadır. Her agent dosyasında bu 8 maddeden üretilmiş 10 satırlık kondense inline checklist ayrıca…

atezer/FMCP · 0 tokens

screen-builder

DS-compliant Figma ekran üretim agent'ı. Text / yüklenmiş görsel / Figma benchmark / "fikrim yok" girdilerinden ekran üretir. "ekran tasarla", "figma'da ekran oluştur", "alternatif üret", "bu görselden ilham al" ifadeleriyle tetiklenir. Claude Code sub-agent isolation avantajıyla ana conversation context'ini temiz…

atezer/FMCP · 91 tokens

Figma MCP Free

Implements Figma designs as code using the Figma MCP Free server. Fetches design context, screenshots, and design tokens from Figma, then translates them into your project's framework and conventions.

karthikyaddana/figma-mcp-free · 44 tokens