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 agentmods add skills/codacy/codacy-skills/setup-coveragenpx skills add codacy/codacy-skills --skill setup-coveragegit clone --depth 1 https://github.com/codacy/codacy-skillsWhat 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 | $0.00113 | $0.02937 |
| Opus 5 | $0.00056 | $0.01469 |
| Sonnet 5 | $0.00023 | $0.00587 |
| Haiku 4.5 | $0.00011 | $0.00294 |
Grade C, and why
setup-coverage scanned grade C with 2 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 2d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
wget -qO - https://coverage.codacy.com/get.sh | sh -s -- report -r <report-file> Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
bash <(curl -Ls https://coverage.codacy.com/get.sh) report -r <coverage-report-file> How it starts
The opening of the file, as written. The whole thing — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Coverage
Glossary: See glossary.md for shared definitions of Codacy concepts (issues, findings, severity, coverage, tools, patterns, etc.).
This skill sets up test coverage reporting in a repository and configures automatic upload to Codacy. It detects what exists, identifies what is missing, and fills the gaps.
Prerequisites
CODACY_PROJECT_TOKENorCODACY_API_TOKENmust be available for coverage uploads (see Authentication)- The repository must be added to Codacy
Workflow
Coverage Setup Progress:
- [ ] Step 1: Detect testing setup
- [ ] Step 2: Detect CI/CD pipeline
- [ ] Step 3: Identify coverage gaps
- [ ] Step 4: Add coverage generation
- [ ] Step 5: Add Codacy coverage upload
- [ ] Step 6: Verify the setup
Step 1: Detect testing setup
Scan the repository to identify:
- Languages in use (check file extensions, build files, package manifests)
- Test frameworks (look for test directories, test files, framework configs):
- JavaScript/TypeScript: Jest, Vitest, Mocha, NYC/Istanbul, c8
- Python: pytest, unittest, coverage.py
- Java: JUnit, JaCoCo, Maven Surefire/Failsafe
- Kotlin: JUnit, JaCoCo (Gradle or Maven)
- Android: JUnit, JaCoCo, Espresso,
createDebugCoverageReport - Go: native
go test - Ruby: RSpec, SimpleCov, Minitest
- C#/.NET: xUnit, NUnit, MSTest, Coverlet, dotCover
- Scala: sbt-jacoco, scoverage
- PHP: PHPUnit
- Swift/Obj-C: XCTest, Xcode Code Coverage
- Existing coverage configuration (NYC config, Jest
collectCoverage,pytest.inicoverage settings, JaCoCo plugin in pom.xml/build.gradle, etc.) - Existing coverage reports (look for
coverage/,lcov.info,cobertura.xml,jacoco*.xml, etc.)
Report findings to the user before proceeding.
Step 2: Detect CI/CD pipeline
Identify which CI/CD system is in use:
| CI/CD | Detection files |
|---|---|
| GitHub Actions | .github/workflows/*.yml |
| GitLab CI | .gitlab-ci.yml |
| CircleCI | .circleci/config.yml |
| Travis CI | .travis.yml |
| Bitbucket Pipelines | bitbucket-pipelines.yml |
| Jenkins | Jenkinsfile |
| Azure DevOps | azure-pipelines.yml |
What ships with it
2 files 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.
- 2d ago First seen · 345 lines · 113 tokens per session scan C 6f4e6ae8a79e
setup-coverage is a skill published in the GitHub repository codacy/codacy-skills (11 stars, last pushed 1mo ago), licensed MIT. It adds 113 tokens to every session and 2,937 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…