Borrowing it
Nothing to install: this file belongs to vepo/issues. 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/vepo/issues/main/.claude/skills/increase-coverage/SKILL.mdgit clone --depth 1 https://github.com/vepo/issuesWrote 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/vepo/issues/increase-coverage)<a href="https://agentmods.dev/skills/vepo/issues/increase-coverage"><img src="https://agentmods.dev/badge/skills/vepo/issues/increase-coverage/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/vepo/issues/increase-coverage"><img src="https://agentmods.dev/badge/skills/vepo/issues/increase-coverage.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.00028 | $0.00336 |
| Opus 5.5 | $0.00011 | $0.00134 |
| Sonnet 5.5 | $0.00006 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
increase-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 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.
What it actually says
You are an expert Java test engineer for Issues. Raise both JaCoCo instruction and branch coverage (target ≥ 80% unless pom.xml defines other thresholds).
Loop
-
Measure
mvn clean verify jacoco:reportReport:
target/jacoco-report/jacoco.xmland HTML undertarget/site/jacoco/. -
Check thresholds Stop when both ≥ 80%: print
✅ Coverage target reached!Otherwise list 5 lowest branch-coverage classes (min 20 instructions).
-
Per class
- Prefer removing genuinely dead code over testing unreachable paths.
- Add
*Test.javaundersrc/test/java/dev/vepo/issues/. - Every test method must assert return values, state changes, or error paths.
- Run single test:
mvn test -Dtest=ClassName#methodName
-
Re-measure after each class:
mvn verify jacoco:report -
Repeat until targets met.
Rules
- Do not delete or weaken existing assertions.
- Record instruction % and branch % in
reports/coverage_log-{sequential}-{dd-MM-yyyy-HH-mm-ss}.md. - Follow
.cursor/rules/issues-testing.mdcfor test placement.
Start the loop now.
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 · 39 lines · 28 tokens per session scan A 37a538525af6
increase-coverage is a skill published in the GitHub repository vepo/issues (8 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 336 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
Cypress v14 Component Testing
Component testing patterns with Cypress v14 including React, Vue, and Angular component mounting, custom mount commands, interaction testing, visual snapshots, and integration with Vite and Webpack bundlers.
Karma Testing
Comprehensive Karma test runner skill for browser-based JavaScript unit testing with Jasmine, Mocha, or QUnit frameworks, real browser execution, coverage reporting, and CI/CD pipeline integration.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
flutter-bloc-state-management
Implement BLoC/Cubit state, events, transitions, and async concurrency in Flutter. Use for BLoC/Cubit feature logic, debounced/cancellable events, state rendering, or bloc tests—not generic widget-only work.
authoring-benchmarks
Design, implement, run, debug, and interpret browser performance benchmarks for Elements components and utilities. Use whenever the user asks to benchmark or performance-test runtime code, create or update a .test.bench.ts file, compare benchmark results, investigate a browser performance regression, understand Vitest…
agent-starters
Verify every starter supported by the stable production NVIDIA Elements CLI from a fresh consumer environment, investigate failures, and prepare at most one focused repair pull request. Use for nightly or scheduled production starter verification and starter availability failures.