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 instructions/thepizzapie/buildersgate/codacygit clone --depth 1 https://github.com/Thepizzapie/BuildersGateWhat 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.00963 | $0.00963 |
| Opus 5 | $0.00481 | $0.00481 |
| Sonnet 5 | $0.00193 | $0.00193 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
BuildersGate codacy.instructions.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.
This is a copy
100% identical to opilot codacy.instructions.md — 55 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codacy Rules
Configuration for AI behavior when interacting with Codacy's MCP Server
CRITICAL: After ANY successful edit_file or reapply operation
- YOU MUST IMMEDIATELY run the
codacy_cli_analyzetool from Codacy's MCP Server for each file that was edited, with: rootPath: set to the workspace pathfile: set to the path of the edited filetool: leave empty or unset- If any issues are found in the new edits, propose and apply fixes for them.
-
NOTE: Failure to follow this rule is considered a critical error.
When you tried to run the codacy_cli_analyze tool and the Codacy CLI is not installed
- Ask the user 'Codacy CLI is not installed. Would you like me to install it now?'
- If the user responds with "yes", run the
codacy_cli_installtool and then continue with the original task - If the user responds with "no", instruct the user that they can disable automatic analysis in the extension settings
- Wait for the user to respond before proceeding with any other actions
After every response
- If you made any file edits in this conversation, verify you ran
codacy_cli_analyzetool from Codacy's MCP Server
When there are no Codacy MCP Server tools available, or the MCP Server is not reachable
- Suggest the user the following troubleshooting steps:
- Try to reset the MCP on the extension
- If the user is using VSCode, suggest them to review their Copilot > MCP settings in Github, under their organization or personal account. Refer them to Settings > Copilot > Enable MCP servers in Copilot. Suggested URL (https://github.com/settings/copilot/features) or https://github.com/organizations/{organization-name}/settings/copilot/features (This can only be done by their organization admins / owners)
- If none of the above steps work, suggest the user to contact Codacy support
Trying to call a tool that needs a rootPath as a parameter
- Always use the standard, non-URL-encoded file system path
CRITICAL: Dependencies and Security Checks
- IMMEDIATELY after ANY of these actions:
- Running npm/yarn/pnpm install
- Adding dependencies to package.json
- Adding requirements to requirements.txt
- Adding dependencies to pom.xml
- Adding dependencies to build.gradle
- Any other package manager operations
- You MUST run the
codacy_cli_analyzetool with: rootPath: set to the workspace pathtool: set to "trivy"file: leave empty or unset- If any vulnerabilities are found because of the newly added packages:
- Stop all other operations
- Propose and apply fixes for the security issues
- Only continue with the original task after security issues are resolved
- EXAMPLE:
- After: npm install react-markdown
- Do: Run codacy_cli_analyze with trivy
- Before: Continuing with any other tasks
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 · 72 lines · 963 tokens per session scan A d45a3281ea30
BuildersGate codacy.instructions.md is an instructions file published in the GitHub repository Thepizzapie/BuildersGate (23 stars, last pushed 2d ago), licensed MIT. It adds 963 tokens to every session, about $0.0048 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to opilot codacy.instructions.md, differing in 55 lines, and is treated as a copy.
Other instructions, from other repositories
build_a_product_agent CLAUDE.md
Instructions for ADW-19/build_a_product_agent, covering claude.md, 项目本质（readme 概览之外）, 目录与编号规范, 文章写作规范（新增/修改文章时必须遵循） and 常用操作.
kungfu AGENTS.md
Instructions for kungfu-systems/kungfu, covering agents.md, start from the person's objective, rules that always apply, load bounded context before changing the repository and execute and verify through shifu.
kungfu CLAUDE.md
Instructions for kungfu-systems/kungfu: Read and follow AGENTS.md before working in this repository. It routes both product use and contribution work to the repository sources of truth, including the requirement that development and build tasks enter through Shifu.
kungfu copilot-instructions.md
Instructions for kungfu-systems/kungfu: Read and follow AGENTS.md before proposing or running changes. It is the shared agent router for this repository, including the canonical Shifu development and build entrypoint.
growmos AGENTS.md
Instructions for codician-team/growmos: This repository keeps a knowledge graph in .growmos/ (entities, typed relations, provenance, profiles, a journal). It is the shared world model that survives context windows. Treat it as memory you read at the start of work and write to as you develop. Zero-config commands.
awesome-agent-infrastructure CLAUDE.md
Instructions for backblaze-labs/awesome-agent-infrastructure, covering claude.md — awesome-agent-infrastructure, what this list is, scope and files, schema, workflow, rules.