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/PMDevSolutions/AureliusWrote 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/pmdevsolutions/aurelius/test-results-analyzer)<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/test-results-analyzer"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/test-results-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/pmdevsolutions/aurelius/test-results-analyzer"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/test-results-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.00043 | $0.01876 |
| Opus 5.5 | $0.00017 | $0.00750 |
| Sonnet 5.5 | $0.00009 | $0.00375 |
| Haiku 4.5 | $0.00004 | $0.00188 |
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 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.
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:
-
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
-
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
-
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
-
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
-
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
-
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:
-
Failure Pattern Analysis:
- Group failures by component
- Identify common error messages
- Track failure frequency
- Correlate with recent changes
- Find environmental factors
-
Performance Trend Analysis:
- Track test execution times
- Identify slowest tests
- Measure parallelization efficiency
- Find performance regressions
- Optimize test ordering
-
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:
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 · 249 lines · 43 tokens per session scan A 9144dd73c9e3
test-results-analyzer is an agent published in the GitHub repository PMDevSolutions/Aurelius (9 stars, last pushed 18d ago), licensed MIT. It adds 43 tokens to every session and 1,876 once invoked, about $0.0002 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-04.
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.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.
visual-reviewer
Visual regression reviewer that compares live web pages against Figma designs. Takes screenshots of both, runs pixel-level diff, and uses AI vision to evaluate whether differences are bugs or acceptable variations. Use before merge or deployment to catch visual regressions.