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/damingdong/opencode-skills-hub/coverage-report-analyzernpx skills add DamingDong/opencode-skills-hub --skill coverage-report-analyzergit clone --depth 1 https://github.com/DamingDong/opencode-skills-hubWrote 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/damingdong/opencode-skills-hub/coverage-report-analyzer)<a href="https://agentmods.dev/skills/damingdong/opencode-skills-hub/coverage-report-analyzer"><img src="https://agentmods.dev/badge/skills/damingdong/opencode-skills-hub/coverage-report-analyzer.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 | $0.00068 | $0.00432 |
| Opus 5 | $0.00034 | $0.00216 |
| Sonnet 5 | $0.00014 | $0.00086 |
| Haiku 4.5 | $0.00007 | $0.00043 |
Grade A, and why
coverage-report-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 5d 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
Coverage Report Analyzer
Overview
This skill provides automated assistance for coverage report analyzer tasks within the Test Automation domain.
When to Use
This skill activates automatically when you:
- Mention "coverage report analyzer" in your request
- Ask about coverage report analyzer patterns or best practices
- Need help with test automation skills covering unit testing, integration testing, mocking, and test framework configuration.
Instructions
- Provides step-by-step guidance for coverage report analyzer
- Follows industry best practices and patterns
- Generates production-ready code and configurations
- Validates outputs against common standards
Examples
Example: Basic Usage Request: "Help me with coverage report analyzer" Result: Provides step-by-step guidance and generates appropriate configurations
Prerequisites
- Relevant development environment configured
- Access to necessary tools and services
- Basic understanding of test automation concepts
Output
- Generated configurations and code
- Best practice recommendations
- Validation results
Error Handling
| Error | Cause | Solution |
|---|---|---|
| Configuration invalid | Missing required fields | Check documentation for required parameters |
| Tool not found | Dependency not installed | Install required tools per prerequisites |
| Permission denied | Insufficient access | Verify credentials and permissions |
Resources
- Official documentation for related tools
- Best practices guides
- Community examples and tutorials
Related Skills
Part of the Test Automation skill category. Tags: testing, jest, pytest, mocking, tdd
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.
- 5d ago First seen · 73 lines · 68 tokens per session scan A 10615ae62bf4
coverage-report-analyzer is a skill published in the GitHub repository DamingDong/opencode-skills-hub (11 stars, last pushed 7mo ago), licensed MIT. It adds 68 tokens to every session and 432 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…