Borrowing it
Nothing to install: this file belongs to organvm-iii-ergon/public-record-data-scrapper. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/organvm-iii-ergon/public-record-data-scrapper/main/.github/instructions/codacy.instructions.mdgit clone --depth 1 https://github.com/organvm-iii-ergon/public-record-data-scrapperWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/organvm-iii-ergon/public-record-data-scrapper/codacy)<a href="https://agentmods.dev/instructions/organvm-iii-ergon/public-record-data-scrapper/codacy"><img src="https://agentmods.dev/badge/instructions/organvm-iii-ergon/public-record-data-scrapper/codacy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/organvm-iii-ergon/public-record-data-scrapper/codacy"><img src="https://agentmods.dev/badge/instructions/organvm-iii-ergon/public-record-data-scrapper/codacy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00939 | $0.00939 |
| Opus 5.5 | $0.00376 | $0.00376 |
| Sonnet 5.5 | $0.00188 | $0.00188 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
public-record-data-scrapper 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 1mo 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
94% identical to aidevops codacy.instructions.md — 59 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 — 69 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.
- 1mo ago Changed · +1 lines 22960882a147
- 1mo ago First seen · 68 lines · 939 tokens per session scan A 3052dd2e6c06
public-record-data-scrapper codacy.instructions.md is an instructions file published in the GitHub repository organvm-iii-ergon/public-record-data-scrapper (8 stars, last pushed 1mo ago), licensed MIT. It adds 939 tokens to every session, about $0.0038 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to aidevops codacy.instructions.md, differing in 59 lines, and is treated as a copy.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.