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/selfagency/opilot/codacygit clone --depth 1 https://github.com/selfagency/opilotWhat 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.00962 | $0.00962 |
| Opus 5 | $0.00481 | $0.00481 |
| Sonnet 5 | $0.00192 | $0.00192 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
opilot 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- mythos codacy.instructions.md — 100% identical, 55 lines differ
- BuildersGate codacy.instructions.md — 100% identical, 55 lines differ
- GDPRShiftLeftMCP codacy.instructions.md — 100% identical, 55 lines differ
- mcp-phpinsights codacy.instructions.md — 88% identical, 62 lines differ
How it starts
The opening of the file, as written. The whole thing — 83 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
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 · 83 lines · 962 tokens per session scan A 7d3063d69d70
opilot codacy.instructions.md is an instructions file published in the GitHub repository selfagency/opilot (90 stars, last pushed 1mo ago), licensed MIT. It adds 962 tokens to every session, about $0.0048 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.
Other instructions, from other repositories
witsy copilot-instructions.md
Copilot instructions for Kochava-Studios/witsy, covering witsy ai assistant - developer guide, project overview, architecture & key components, core structure and build system (electron forge + vite).
witsy AGENTS.md
AGENTS.md instructions for Kochava-Studios/witsy, covering witsy ai assistant - developer guide, project overview, architecture & key components, core structure and build system (electron forge + vite).
witsy CLAUDE.md
Claude Code instructions for Kochava-Studios/witsy, covering witsy ai assistant - developer guide, project overview, architecture & key components, core structure and build system (electron forge + vite).
ollama CLAUDE.md
Instructions for ollama/ollama: See AGENTS.md for the shared agent instructions for this repository.
pocketpaw CLAUDE.md
Instructions for pocketpaw/pocketpaw, covering claude.md, project overview, knowledge base, search the kb from terminal and show a specific module's wiki.
vscode-peacock AGENTS.md
Instructions for johnpapa/vscode-peacock, covering peacock — agent guide, project overview, repository structure, tech stack and build & run.