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/configure-codacynpx skills add codacy/codacy-skills --skill configure-codacygit 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.00133 | $0.11639 |
| Opus 5 | $0.00067 | $0.05819 |
| Sonnet 5 | $0.00027 | $0.02328 |
| Haiku 4.5 | $0.00013 | $0.01164 |
Grade C, and why
configure-codacy scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .codacy/tmp How it starts
The opening of the file, as written. The whole thing — 832 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure Codacy
Glossary: See glossary.md for shared definitions of Codacy concepts (issues, findings, severity, coverage, tools, patterns, etc.).
This skill tailors Codacy configuration to a project's actual stack and coding conventions. It discovers the repository's languages and frameworks, initializes a broad set of tools and patterns, runs analysis, then intelligently cuts noise — producing a clean, high-signal configuration with a full audit trail of what changed and why.
Prerequisites
- Codacy Analysis CLI (
codacy-analysis) withdiscoverandinit --autosupport. If the CLI does not support these commands, update it running:npm i -g @codacy/analysis-cli. Seecodacy-analysis-clifor setup. - Codacy Cloud CLI (
codacy) — needed to know if the repo is on Codacy Cloud and if so, fetch issues from the cloud-only tools. Seecodacy-cloud-clifor setup.
Both CLIs share credentials at ~/.codacy/credentials, so a single login covers both.
How configuration works
All configuration is done locally via .codacy/codacy.config.json. Edit the file, run analysis, see results instantly — no push or cloud reanalysis needed. Once tuned, the configuration can be imported to Codacy Cloud in one step.
The key principle: start broad, then cut noise using data. Initialize with maximum pattern coverage via init --auto, run analysis to see the full issue landscape, then use the severity/category distribution to decide what to disable or tune.
Read the config format reference for the full schema before editing — field names matter (e.g., the exclusion field is exclude, not excludePaths). To disable a pattern, remove it from the patterns array. To disable a tool, remove the entire tool entry.
Organization standards take precedence. If a pattern is enforced by a Coding Standard at the organization level, it cannot be changed at the repository level.
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 · 832 lines · 133 tokens per session scan C a8aadb16082f
configure-codacy is a skill published in the GitHub repository codacy/codacy-skills (11 stars, last pushed 1mo ago), licensed MIT. It adds 133 tokens to every session and 11,639 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.