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 girijashankarj/cursor-handbook --skill coverage-improvementgit clone --depth 1 https://github.com/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/coverage-improvement)<a href="https://agentmods.dev/skills/girijashankarj/cursor-handbook/coverage-improvement"><img src="https://agentmods.dev/badge/skills/girijashankarj/cursor-handbook/coverage-improvement/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/girijashankarj/cursor-handbook/coverage-improvement"><img src="https://agentmods.dev/badge/skills/girijashankarj/cursor-handbook/coverage-improvement.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.00030 | $0.00330 |
| Opus 5 | $0.00015 | $0.00165 |
| Sonnet 5 | $0.00006 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
coverage-improvement 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 6d 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
Skill: Improve Test Coverage
Trigger
When coverage is below {{CONFIG.testing.coverageMinimum}}% or user asks to improve coverage.
Steps
Step 1: Analyze Current Coverage
- Run coverage report:
{{CONFIG.testing.coverageCommand}} - Identify files below {{CONFIG.testing.coverageMinimum}}% coverage
- Rank by: business criticality × uncovered percentage
Step 2: Identify Gaps
For each uncovered file:
- List uncovered functions/methods
- List uncovered branches (if/else, switch)
- List uncovered error paths
- Determine which gaps are most important
Step 3: Write Missing Tests
Priority order:
- Error handling paths
- Business logic branches
- Edge cases (null, empty, boundary)
- Success paths (usually already covered)
For each test:
- Follow AAA pattern (Arrange-Act-Assert)
- Use descriptive test names
- Mock external dependencies
- Assert specific behaviors, not implementation
Step 4: Verify Coverage
- Run coverage again:
{{CONFIG.testing.coverageCommand}} - Confirm target met: ≥{{CONFIG.testing.coverageMinimum}}%
- All new tests pass
Completion
Coverage meets or exceeds {{CONFIG.testing.coverageMinimum}}% with meaningful tests.
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.
- 6d ago First seen · 45 lines · 30 tokens per session scan A 7139301c806f
coverage-improvement is a skill published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 10d ago), licensed MIT. It adds 30 tokens to every session and 330 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
mockito
Use when generating mocks, stubbing methods, verifying interactions, capturing arguments, or choosing between mocks, fakes, and real objects (Mockito).
mocktail
Use when creating mocks, stubbing methods, verifying interactions, registering fallback values, or choosing between mocks, fakes, and real objects (Mocktail).
iterate-agent-harness
Turn an agent failure—premature stop, false completion, gamed check, missed file, broken handoff—into a durable rule/skill/hook/CI guard plus regression test. Use when "the agent stopped early again", "it gamed the test", or "add a guard so this doesn't recur". App bugs → workflow-fix-and-ship.
test-data-factory-builder
Creates factories and builders for generating consistent, composable test data with realistic values and relationship handling. Use for "test factories", "test data builders", "fixture factories", or "test data generation".
unit-test-generator
Generates comprehensive unit tests with AAA pattern (Arrange-Act-Assert), edge cases, error scenarios, and coverage analysis. Creates test files matching source structure with complete test suites. Use for "unit testing", "test generation", "Jest tests", or "test coverage".