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/armanzeroeight/fastagent-pluginsWrote 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/commands/armanzeroeight/fastagent-plugins/coverage-report)<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/coverage-report"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/coverage-report/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/commands/armanzeroeight/fastagent-plugins/coverage-report"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/coverage-report.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.00010 | $0.00991 |
| Opus 5.5 | $0.00004 | $0.00396 |
| Sonnet 5.5 | $0.00002 | $0.00198 |
| Haiku 4.5 | $0.00001 | $0.00099 |
Grade A, and why
coverage-report 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coverage Report
Context
- Project type: !
[ -f "package.json" ] && echo "Node.js" || [ -f "pyproject.toml" ] && echo "Python" || [ -f "go.mod" ] && echo "Go" || echo "Unknown" - Test framework: !
[ -f "package.json" ] && (grep -q "jest" package.json && echo "Jest" || grep -q "vitest" package.json && echo "Vitest" || echo "Unknown") || [ -f "pyproject.toml" ] && echo "pytest" || echo "Unknown" - Coverage files: !
find . -name "coverage" -o -name "htmlcov" -o -name "coverage.out" 2>/dev/null | head -5
Your Task
Generate a comprehensive test coverage report and provide analysis with recommendations.
Arguments
$1(optional): Report format -terminal,html,json, orall(default:terminal)
Steps
-
Generate coverage report based on framework:
Jest:
npm test -- --coverage --coverageReporters=text --coverageReporters=html --coverageReporters=jsonVitest:
vitest run --coveragepytest:
pytest --cov=src --cov-report=term-missing --cov-report=html --cov-report=jsonGo:
go test -coverprofile=coverage.out ./... go tool cover -func=coverage.out -
Display terminal report with key metrics:
- Overall coverage percentage
- Line coverage
- Branch coverage
- Function coverage
- Statement coverage
-
Analyze coverage data and identify:
- Files with 0% coverage
- Files with <50% coverage
- Critical files with low coverage
- Uncovered branches and error paths
-
Provide recommendations:
High Priority (address first):
- List files with 0% coverage
- Identify critical business logic with low coverage
- Highlight security-related code without tests
Medium Priority (address next):
- List files with <50% coverage
- Identify API endpoints without tests
- Highlight database operations without tests
Low Priority (address if time permits):
- List files with 50-70% coverage
- Identify UI components without tests
- Highlight utility functions with partial coverage
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 · 142 lines · 10 tokens per session scan A 24cbc5d8e671
coverage-report is a command published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 991 once invoked, about $0.0000 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-03.
Other commands, from other repositories
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
run-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.
lock-e2e
Promote a verified action into a frozen, locked e2e regression test. Runs the action once strict (no repair) via cdplocke2etest and freezes it to .rn-agent/e2e/ .yaml only if it passes. v1 supports param-free actions only.
quality-check
Execute a comprehensive quality gate check (lint, test, build, format) before allowing code to merge.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
run-test
Execute AI agent test script in real browser.