Borrowing it
Nothing to install: this file belongs to AsiaOstrich/EngramGraph. 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/AsiaOstrich/EngramGraph/main/.agents/skills/test-coverage-assistant/SKILL.mdgit clone --depth 1 https://github.com/AsiaOstrich/EngramGraphWrote 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/asiaostrich/engramgraph/test-coverage-assistant)<a href="https://agentmods.dev/skills/asiaostrich/engramgraph/test-coverage-assistant"><img src="https://agentmods.dev/badge/skills/asiaostrich/engramgraph/test-coverage-assistant/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/asiaostrich/engramgraph/test-coverage-assistant"><img src="https://agentmods.dev/badge/skills/asiaostrich/engramgraph/test-coverage-assistant.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.00114 | $0.01067 |
| Opus 5.5 | $0.00046 | $0.00427 |
| Sonnet 5.5 | $0.00023 | $0.00213 |
| Haiku 4.5 | $0.00011 | $0.00107 |
Grade A, and why
coverage 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 14d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Coverage Assistant | 測試覆蓋率助手
Analyze test coverage across multiple dimensions and provide actionable recommendations.
多維度分析測試覆蓋率並提供可執行的建議。
Related: For requirement-level coverage (which AC have tests?), use
/ac-coverageinstead. This skill (/coverage) focuses on code-level coverage (lines, branches, functions).相關：如需需求層級覆蓋率（哪些 AC 有對應測試？），請改用
/ac-coverage。此技能（/coverage）專注於程式碼層級覆蓋率。
Coverage Dimensions | 覆蓋率維度
| Dimension | What it Measures | 測量內容 |
|---|---|---|
| Line | Lines of code executed | 執行的程式碼行數 |
| Branch | Decision paths taken | 決策路徑覆蓋 |
| Function | Functions called | 呼叫的函數 |
| Statement | Statements executed | 執行的陳述式 |
8-Dimension Framework | 八維度框架
- Code Coverage - Lines, branches, functions
- Requirement Coverage - All requirements have tests
- Risk Coverage - High-risk areas prioritized
- Integration Coverage - Component interaction paths
- Edge Case Coverage - Boundary conditions tested
- Error Coverage - Error handling paths verified
- Permission Coverage - Access control scenarios
- AI Generation Quality - AI-generated test effectiveness
Coverage Targets | 覆蓋率目標
| Level | Coverage | Use Case | 適用場景 |
|---|---|---|---|
| Minimum | 60% | Legacy code | 遺留程式碼 |
| Standard | 80% | Most projects | 大多數專案 |
| High | 90% | Critical systems | 關鍵系統 |
| Critical | 95%+ | Safety-critical | 安全關鍵 |
Workflow | 工作流程
- Run coverage tool - Generate coverage report | 產生覆蓋率報告
- Analyze gaps - Identify untested areas | 識別未測試區域
- Prioritize - Rank by risk and importance | 依風險排序
- Recommend tests - Suggest specific tests to add | 建議新增測試
- Track progress - Monitor coverage over time | 追蹤進度
Usage | 使用方式
/coverage - Run full coverage analysis | 執行完整覆蓋率分析
/coverage src/auth - Analyze specific module | 分析特定模組
/coverage --recommend - Get test recommendations | 取得測試建議
What ships with it
1 file 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.
- 14d ago First seen · 88 lines · 114 tokens per session scan A c3c718a30e6e
coverage is a skill published in the GitHub repository AsiaOstrich/EngramGraph (3 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 1,067 once invoked, about $0.0005 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-10-16.
Other skills, from other repositories
kivgraph
Use Kivgraph's local MCP server to search symbols, read their source, and follow references, dependencies, cross-repository consumers and graph status in the indexed code graph.
mushroom
Live graph memory for agents — query and create entities, derive relationships by rule, explain why two things are associated, read the graph at a past commit, ask what a change would do, and answer as one role. Trigger on: memory, remember, recall, relationship, entity, association, why are X and Y related, as of…
potpie-debug-memory
Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.
potpie-project-preferences
Use before writing, modifying, reviewing, refactoring, or testing code so repo/project preferences surface: error handling, file structure, frameworks, logging, dependency choices, testing, security, API style, and naming. Also use after code work when a reusable project preference should be recorded.
omnigraph
Operate OmniGraph graphs and deployments. Use for .pg schemas, .gq queries, OmniGraph CLI commands, file:///s3:///az:// graph URIs, cluster.yaml, operator config, bearer-authenticated servers, graph-backed knowledge or memory, Blob values, embeddings, branches, commits, and change feeds. Apply especially before schema…
code-graph
This skill should be used when understanding code structure, finding dependencies between functions/classes, tracing call graphs, or exploring code relationships. Trigger phrases include 'code graph', 'call graph', 'who calls', 'what calls', 'find dependencies', 'code structure', 'inheritance', 'find paths'.