codacy-skills CLAUDE.md

Project instructions for creating and maintaining Codacy skills, including their folder structure, filenames, and required YAML metadata. Codacy is a service for automated code-quality analysis.

In plain words
What is it for?
They are for adding or updating Codacy skills and documenting when each skill should be used.
Why use it?
They help contributors create skills that follow the repository's naming, organization, and documentation rules.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/codacy/codacy-skills/claude-md
Clone the repo
git clone --depth 1 https://github.com/codacy/codacy-skills
Per session 857 This file is loaded in full into every session.
When invoked 857 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00857 $0.00857
Opus 5 $0.00428 $0.00428
Sonnet 5 $0.00171 $0.00171
Haiku 4.5 $0.00086 $0.00086

Measured 2d ago against content hash 62806eadd841, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

codacy-skills CLAUDE.md 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 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.

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.

CLAUDE.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md — Project instructions for Claude

This is a collection of Claude skills for working with the Codacy CLI.

Project structure

/
├── CLAUDE.md               # This file
├── README.md               # Project overview and installation
├── CONTRIBUTING.md         # How to contribute
├── LICENSE                 # MIT
├── CODE_OF_CONDUCT.md      # Community standards
├── .claude-plugin/         # Plugin manifest
│   ├── plugin.json         # Plugin metadata
│   └── marketplace.json    # Marketplace catalog
└── skills/                 # All Agent Skills
    └── <skill-name>/       # One folder per skill
        ├── SKILL.md        # Required — YAML frontmatter + instructions
        └── references/     # Optional — detailed docs

Skill authoring rules

Structure

  • Folder name and name field: kebab-case only (lowercase, hyphens, no spaces or capitals)
  • File must be exactly SKILL.md (case-sensitive)
  • No README.md inside skill folders
  • Keep SKILL.md under 500 lines; move verbose content to references/ files

YAML frontmatter (required fields)

---
name: skill-name-in-kebab-case
description: Third-person description of what it does and when to use it. Include trigger phrases.
---
  • description: under 1024 characters, no XML tags (< >), written in third person
  • Do not use reserved names: anthropic-*, claude-*

Writing good descriptions

Include: what the skill does + when to trigger it + key trigger phrases.

Good:

Queries Codacy issues, findings, and pull request data using the Codacy CLI.
Use when the user asks about code issues, security findings, pull request analysis,
or wants to run Codacy commands.

Bad:

Helps with Codacy.

Writing good instructions

  • Be specific and actionable — avoid vague directives
  • Use numbered steps for ordered workflows
  • Set appropriate freedom: exact commands for fragile operations, flexible guidance for context-dependent ones
  • Include error handling for common failures
  • Reference detailed content via links to references/ files rather than inlining everything
  • Provide concrete examples

Read the full file on GitHub · 89 lines

Changes

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.

  1. 2d ago First seen · 89 lines · 857 tokens per session scan A 62806eadd841

Subscribe to this mod's changes

codacy-skills CLAUDE.md is an instructions file published in the GitHub repository codacy/codacy-skills (11 stars, last pushed 1mo ago), licensed MIT. It adds 857 tokens to every session, about $0.0043 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-08-30.