Borrowing it
Nothing to install: this file belongs to jmrplens/gitlab-mcp-server. 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/jmrplens/gitlab-mcp-server/main/.github/skills/increase-test-coverage/SKILL.mdgit clone --depth 1 https://github.com/jmrplens/gitlab-mcp-serverWrote 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/jmrplens/gitlab-mcp-server/increase-test-coverage)<a href="https://agentmods.dev/skills/jmrplens/gitlab-mcp-server/increase-test-coverage"><img src="https://agentmods.dev/badge/skills/jmrplens/gitlab-mcp-server/increase-test-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/jmrplens/gitlab-mcp-server/increase-test-coverage"><img src="https://agentmods.dev/badge/skills/jmrplens/gitlab-mcp-server/increase-test-coverage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 328 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Privilege Escalation · line 392 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.05865 |
| Opus 5.5 | $0.00034 | $0.02346 |
| Sonnet 5.5 | $0.00017 | $0.01173 |
| Haiku 4.5 | $0.00008 | $0.00587 |
Grade B, and why
increase-test-coverage scanned grade B with 1 finding 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 today.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Tests run as root.** Permission bits make nothing fail. A read that must fail even for root uses a broken symlink (`os.Symlink` to a missing target); a write that must fail goes through a seam. How it starts
The opening of the file, as written. The whole thing — 502 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Increase Test Coverage
Primary Directive
Systematically increase Go test coverage to 100% per touched package, preexisting code included, using a structured Research → Plan → Implement pipeline; every function that stays below 100% is named in the report with its reason. Generate comprehensive, buildable, passing tests that follow project conventions and use proper mocks for external dependencies.
All tests must:
- Compile and pass on the first run
- Use existing test helpers and patterns found in the codebase
- Mock external dependencies (GitLab API) via
httptest - Follow table-driven test patterns with
t.Run()subtests - Cover happy paths, edge cases, and error scenarios
- Include documentation (doc comment) explaining what each test validates and why
- Be verified against false passes (assertions that never fail)
- Be written in English per project language policy
Execution Context
This skill is designed for the Test Expert agent or any agent tasked with increasing test coverage. It operates on Go codebases that use the standard testing package and net/http/httptest; this project has no testify dependency, so assertions are plain t.Errorf / t.Fatalf.
Pipeline Overview
flowchart TD
start[Increase test coverage]
research[Research\nMeasure coverage and analyze gaps]
plan[Plan\nPrioritize gaps by package]
implement[Implement\nWrite tests per phase]
build[Build\ngolangci-lint and go build]
test[Test\ngo test]
fix[Fix\nRepair errors]
start --> research --> plan --> implement
implement --> build
implement --> test
implement --> fix
fix --> build
fix --> test
Phase 1: Research
Thoroughly analyze the codebase and measure current coverage before writing any tests.
Step 1: Measure Baseline Coverage
Run coverage analysis for the entire project:
go test -coverprofile=coverage.out ./...
go tool cover -func=coverage.out
Record the per-package and per-function coverage percentages. This is the baseline.
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.
- today Changed · +4 lines 99626b9f8449
- 15d ago Changed eece0e4531e2
- 16d ago Changed · -1 lines 7ec56114167d
- 22d ago Changed 6a4efe9a76a5
- 27d ago Changed 6e5a1b481fb3
- 1mo ago Changed · +8 lines fc612b3a6793
- 1mo ago Changed 39ec9ec7d117
- 1mo ago Changed · +74 lines · +12 tokens per session scan A → B 1c17eee5f17d
- 1mo ago First seen · 417 lines · 72 tokens per session scan A c04f73db35d3
increase-test-coverage is a skill published in the GitHub repository jmrplens/gitlab-mcp-server (46 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 5,865 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
go-testing
Use when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff. Also use when a user asks to write a test for a Go function, even if they don't mention specific patterns like table-driven tests or subtests. Does…
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
go-test-implementation
Use for test-only changes or non-routine fixtures and harnesses, selecting cases and assertions from accepted behavior during implementation.
review-coverage
Use when the user asks for a coverage review, test coverage analysis, coverage gap analysis, uncovered code review, or wants to know what new/changed Go code is missing tests. Runs go test -coverprofile against the resolved scope and reports uncovered functions in changed Go files, grouped by package, with severity…
Go Testing Patterns
Go testing with testing package, table-driven tests, subtests, benchmarks, test fixtures, httptest, and testify assertions.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…