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 skills add ArabelaTso/Skills-4-SE --skill coverage-enhancergit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/arabelatso/skills-4-se/coverage-enhancer)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/coverage-enhancer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/coverage-enhancer/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/arabelatso/skills-4-se/coverage-enhancer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/coverage-enhancer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00084 | $0.04182 |
| Opus 5 | $0.00042 | $0.02091 |
| Sonnet 5 | $0.00017 | $0.00836 |
| Haiku 4.5 | $0.00008 | $0.00418 |
Grade A, and why
coverage-enhancer 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 10d 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 — 704 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coverage Enhancer
Analyze existing tests and source code to identify coverage gaps, then suggest specific additional tests to improve overall test coverage and code quality.
Core Capabilities
1. Coverage Gap Analysis
Identify untested areas in source code:
- Uncovered lines - Code never executed by tests
- Uncovered branches - Conditional paths not tested
- Uncovered functions - Methods/functions without tests
- Missing error handling tests - Exception paths not verified
- Untested edge cases - Boundary conditions not covered
- Insufficient scenarios - Limited test diversity
2. Existing Test Analysis
Understand current test coverage by:
- Parsing existing test files
- Identifying tested functions and methods
- Recognizing test patterns and frameworks
- Detecting coverage tools in use
- Analyzing test quality and completeness
3. Test Suggestion Generation
Generate specific, actionable test recommendations:
- Complete test code in the project's framework
- Clear test names describing what's being tested
- Setup, execution, and assertion steps
- Integration with existing test structure
- Prioritized by coverage impact
Coverage Analysis Workflow
Step 1: Analyze Existing Tests
Read and understand the current test suite:
Identify test framework:
# pytest
def test_something():
assert result == expected
# unittest
class TestSomething(unittest.TestCase):
def test_method(self):
self.assertEqual(result, expected)
Map tested functionality:
- Which functions/methods have tests?
- What scenarios are covered?
- What assertions are made?
- What inputs are tested?
Identify test patterns:
- Naming conventions
- Setup/teardown patterns
- Fixture usage
- Mock/stub patterns
Step 2: Analyze Source Code
Examine the implementation to find gaps:
Identify code paths:
def process(value):
if value < 0: # Branch 1
raise ValueError
elif value == 0: # Branch 2
return None
else: # Branch 3
return value * 2
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.
- 10d ago First seen · 704 lines · 84 tokens per session scan A 21ba040189e7
coverage-enhancer is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (251 stars, last pushed 19d ago), licensed Apache-2.0. It adds 84 tokens to every session and 4,182 once invoked, about $0.0004 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
review-ugc-render
Mandatory pre-publish review gate for a UGC video render. Transcribes the finished render's AUDIO with Whisper and word-diffs it against the approved spoken script, then gates setfinalrender — blocking a render whose generated audio mis-voices a word (e.g. the approved "human-vetted" spoken as "human witted"), drops…
test-generator
A test-writing helper that creates unit or integration tests from the code's actual behavior and contracts. Unit tests check small pieces of code, while integration tests check how real components work together.
testing-r-packages
Best practices for writing R package tests using testthat version 3+. Use when writing, organizing, or improving tests for R packages. Covers test structure, expectations, fixtures, snapshots, mocking, and modern testthat 3 patterns including self-sufficient tests, proper cleanup with withr, and snapshot testing.
r-package-development
R package development with devtools, testthat, and roxygen2. Use when the user is working on an R package, running tests, writing documentation, or building package infrastructure.
111-java-maven-dependencies
Use when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency support (JavaMoney) — and want a…
130-java-testing-strategies
Use when you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary conditions. This should trigger for requests such as Review Java code for testing strategies; Apply RIGHT-BICEP testing strategies in Java code…