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.
npx agentmods add skills/summarybotng/summarybot-ng/test-reporting-analyticsnpx skills add summarybotng/summarybot-ng --skill test-reporting-analyticsgit clone --depth 1 https://github.com/summarybotng/summarybot-ngWrote 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/skills/summarybotng/summarybot-ng/test-reporting-analytics)<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/test-reporting-analytics"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/test-reporting-analytics.svg" alt="Measured on agentmods" 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.00041 | $0.01446 |
| Opus 5 | $0.00020 | $0.00723 |
| Sonnet 5 | $0.00008 | $0.00289 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
test-reporting-analytics 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 2d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Reporting & Analytics
<default_to_action> When building test reports:
- DEFINE audience (dev team vs executives)
- CHOOSE key metrics (max 5-7)
- SHOW trends (not just snapshots)
- HIGHLIGHT actions (what to do about it)
- AUTOMATE generation
Dashboard Quick Setup:
+------------------+------------------+------------------+
| Tests Passed | Code Coverage | Flaky Tests |
| 1,247/1,250 ✅ | 82.3% ⬆️ +2.1% | 1.2% ⬇️ -0.3% |
+------------------+------------------+------------------+
| Critical Bugs | Deploy Freq | MTTR |
| 0 open ✅ | 12x/day ⬆️ | 2.3h ⬇️ |
+------------------+------------------+------------------+
Key Metrics by Audience:
- Dev Team: Pass rate, flaky %, execution time, coverage gaps
- QE Team: Defect detection rate, test velocity, automation ROI
- Leadership: Escaped defects, deployment frequency, quality cost </default_to_action>
Quick Reference Card
Essential Metrics
| Category | Metric | Target |
|---|---|---|
| Execution | Pass Rate | >98% |
| Execution | Flaky Test % | <2% |
| Execution | Suite Duration | <10 min |
| Coverage | Line Coverage | >80% |
| Coverage | Branch Coverage | >70% |
| Quality | Escaped Defects | <5/release |
| Quality | MTTR | <4 hours |
| Efficiency | Automation Rate | >90% |
Trend Indicators
| Symbol | Meaning | Action |
|---|---|---|
| ⬆️ | Improving | Continue current approach |
| ⬇️ | Declining | Investigate root cause |
| ➡️ | Stable | Maintain or improve |
| ⚠️ | Threshold breach | Immediate attention |
Report Types
Real-Time Dashboard
Live quality status for CI/CD
- Build status (green/red)
- Test results (pass/fail counts)
- Coverage delta
- Flaky test alerts
Sprint Summary
## Sprint 47 Quality Summary
### Metrics
| Metric | Value | Trend |
|--------|-------|-------|
| Tests Added | +47 | ⬆️ |
| Coverage | 82.3% | ⬆️ +2.1% |
| Bugs Found | 12 | ➡️ |
| Escaped | 0 | ✅ |
### Highlights
- ✅ Zero escaped defects
- ⚠️ E2E suite now 45min (target: 30min)
### Actions
1. Optimize slow E2E tests
2. Add coverage for payment module
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 221 lines · 41 tokens per session scan A db54a602ee63
test-reporting-analytics is a skill published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 1,446 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-03.
Other skills, from other repositories
agent-evaluation-reporting
Use when summarizing agent evaluations where autonomous, assisted, failed, timed-out, or invalid outcomes must remain distinct and comparable.
building-soc-metrics-and-kpi-tracking
Builds SOC performance metrics and KPI tracking dashboards measuring Mean Time to Detect (MTTD), Mean Time to Respond (MTTR), alert quality ratios, analyst productivity, and detection coverage using SIEM data. Use when SOC leadership needs operational visibility, continuous improvement tracking, or executive-level…
business-intelligence-expert
Build comprehensive business intelligence solutions including data warehouses, ETL pipelines, interactive dashboards, and analytical reporting systems. Use when the user mentions BI, data warehousing, star or snowflake schemas, OLAP cubes, ETL/ELT pipelines, dashboards, KPIs, or analytical reporting.
sla-report
Generate a per-monitor SLA report for a time range — uptime percentage, total downtime, and incident count per monitor — formatted as Markdown for sharing in Confluence, Slack, or post-mortem docs.
Campaign Analyzer
Analyze marketing campaign performance and extract actionable insights.
Advanced Allure Reporting
Advanced Allure test reporting with custom categories, environment info, test history trends, flaky test detection, and CI/CD dashboard integration.