Borrowing it
Nothing to install: this file belongs to layer1labs/specsmith. 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/layer1labs/specsmith/main/.agents/skills/testing-coverage-reporting/SKILL.mdgit clone --depth 1 https://github.com/layer1labs/specsmithWrote 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/layer1labs/specsmith/testing-coverage-reporting)<a href="https://agentmods.dev/skills/layer1labs/specsmith/testing-coverage-reporting"><img src="https://agentmods.dev/badge/skills/layer1labs/specsmith/testing-coverage-reporting/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/skills/layer1labs/specsmith/testing-coverage-reporting"><img src="https://agentmods.dev/badge/skills/layer1labs/specsmith/testing-coverage-reporting.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.00018 | $0.00369 |
| Opus 5.5 | $0.00007 | $0.00148 |
| Sonnet 5.5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
testing-coverage-reporting 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 2mo 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.
What it actually says
Testing Coverage Reporting
This skill enables specsmith projects to generate and track test coverage reports while maintaining governance compliance.
Requirements Covered
- REQ-108: Testing Coverage Reporting
- Allows specsmith projects to generate and track test coverage reports with human approval
Integration Capabilities
Coverage Features
- Code coverage measurement and reporting
- Coverage threshold enforcement
- Coverage trend analysis
- Coverage report generation in multiple formats
- Integration with coverage tools (pytest-cov, Istanbul, etc.)
- Coverage data storage and retrieval
Governance Requirements
- Human approval required for coverage reporting
- Configuration management with governance controls
- Approval-based coverage thresholds
- Audit logging of coverage activities
Usage Examples
# Initialize coverage reporting
specsmith skill install testing-coverage-reporting
# Configure coverage settings
specsmith test coverage configure --threshold 80 --format html
# Generate coverage report
specsmith test coverage generate --suite e2e-tests --format html
Configuration
The skill requires the following configuration in scaffold.yml:
coverage:
threshold: 80
format: "html"
include_uncovered: false
generate_on_success: true
generate_on_failure: true
retention_days: 30
Security Considerations
- All coverage reporting requires human approval
- Coverage data must be properly secured
- Access controls for coverage reports must be enforced
- Sensitive code paths must be handled appropriately
Compliance Requirements
- Follow security best practices for coverage reporting
- Maintain audit logs of all coverage activities
- Ensure proper retention and deletion policies
- Enforce approval-based coverage reporting settings
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.
- 2mo ago First seen · 71 lines · 18 tokens per session scan A 4b7e13abc0b4
testing-coverage-reporting is a skill published in the GitHub repository layer1labs/specsmith (8 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 369 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
responsive-audit
Responsive audit: test pages at 375/768/1024px breakpoints via Playwright. Checks overflow, tap targets, sidebar collapse, text reflow, WCAG 1.4.4 zoom.
test-audit
Static test-suite quality audit - coverage from lcov/Istanbul/Cobertura/go/tarpaulin reports, pyramid shape (unit/integration/e2e ratio), anti-patterns (.only leaks, skipped tests, no-assertion tests, hardcoded sleeps). Stack-aware across 11 supported stacks.
team-qa
Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.
regression-suite
Map test coverage to GDD critical paths, find fixed bugs lacking regression tests, flag drift from new features.
soak-test
Soak test protocol for extended play — what to observe and log for slow leaks, fatigue, late-appearing edge cases.
validate
Validate Semantica pipelines, extraction quality, graph schemas, and ontology consistency. Returns structured error/warning checklists. Uses PipelineValidator, PipelineBuilder.validatepipeline(), GraphValidator, and OntologyValidator. Sub-commands: pipeline, step, dependencies, extraction, graph, ontology, performance.