warp-sql-server-mcp codacy.instructions.md

Instructions for how an AI agent should work with Codacy's code-analysis service. Code analysis checks source files for potential quality and security problems.

In plain words
What is it for?
Analyzing changed files with Codacy, comparing findings with a previous baseline, and repeating fixes and checks when needed.
Why use it?
It ensures edited files are analyzed immediately and that newly introduced issues are addressed or reported.

Instructions file for GitHub Copilot

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/egarcia74/warp-sql-server-mcp/codacy
Clone the repo
git clone --depth 1 https://github.com/egarcia74/warp-sql-server-mcp

Made for: GitHub Copilot.

Per session 1,110 This file is loaded in full into every session.
When invoked 1,110 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.01110 $0.01110
Opus 5 $0.00555 $0.00555
Sonnet 5 $0.00222 $0.00222
Haiku 4.5 $0.00111 $0.00111

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

Security

Grade A, and why

warp-sql-server-mcp 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.

.github/instructions/codacy.instructions.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 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_analyze tool from Codacy's MCP Server for each file that was edited, with:
  • rootPath: set to the workspace path
  • file: set to the path of the edited file
  • tool: leave empty or unset
  • Compare results with a baseline captured before editing when one is available, and distinguish pre-existing findings from findings introduced by the edit.
  • If any issues are found in the new edits, propose and apply fixes for them.
  • Limit the fix-and-reanalyze cycle to three attempts per edited file.
  • Stop retrying when the findings remain unchanged, or when the retry limit is reached, and report any unresolved findings to the user.
  • 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_install tool. After installation succeeds, retry the interrupted codacy_cli_analyze call with the original arguments, then continue with the original task.
  • If the user responds with "no", explain that automatic analysis can be disabled 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_analyze tool 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 they 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 or owners.)
  • If none of the above steps work, suggest the user contact Codacy support.

Read the full file on GitHub · 98 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 · 98 lines · 1,110 tokens per session scan A 02a01a9c3497

Subscribe to this mod's changes

warp-sql-server-mcp codacy.instructions.md is an instructions file published in the GitHub repository egarcia74/warp-sql-server-mcp (5 stars, last pushed 2d ago), licensed MIT. It adds 1,110 tokens to every session, about $0.0056 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-31.