mcp-phpinsights: Instructions file for GitHub Copilot

.github/instructions/codacy.instructions.md

mcp-phpinsights codacy.instructions.md is an instructions file for GitHub Copilot from salahmyn/mcp-phpinsights. It costs 822 tokens per session, scanned A, a copy of aidevops codacy.instructions.md, MIT.

Configuration rules for an AI coding assistant that uses Codacy, a code-quality checking service, through its MCP connection.

In plain words
What is it for?
Use it when editing files with Codacy's MCP Server so each changed file is analyzed and reported issues can be fixed.
Why use it?
It makes the assistant check edited files for code-quality problems immediately after changes and explains what to do if the connection is unavailable.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is salahmyn/mcp-phpinsights's own configuration. It tells GitHub Copilot how to work on mcp-phpinsights itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-phpinsights configures →

Reuse

Borrowing it

Nothing to install: this file belongs to salahmyn/mcp-phpinsights. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/salahmyn/mcp-phpinsights/main/.github/instructions/codacy.instructions.md
Clone the repo
git clone --depth 1 https://github.com/salahmyn/mcp-phpinsights

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for mcp-phpinsights codacy.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/salahmyn/mcp-phpinsights/codacy/github.svg)](https://agentmods.dev/instructions/salahmyn/mcp-phpinsights/codacy)
Your own site
<a href="https://agentmods.dev/instructions/salahmyn/mcp-phpinsights/codacy"><img src="https://agentmods.dev/badge/instructions/salahmyn/mcp-phpinsights/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.

agentmods 80×15 button for mcp-phpinsights codacy.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/salahmyn/mcp-phpinsights/codacy"><img src="https://agentmods.dev/badge/instructions/salahmyn/mcp-phpinsights/codacy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 822 This file is loaded in full into every session.
When invoked 822 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 80% copy Near-identical to another mod 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.1 $0.00822 $0.00822
Opus 5.5 $0.00329 $0.00329
Sonnet 5.5 $0.00164 $0.00164
Haiku 4.5 $0.00082 $0.00082

Measured 1mo ago against content hash 5a09c776a35a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mcp-phpinsights 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.

Origin

This is a copy

80% identical to aidevops codacy.instructions.md — 69 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.

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

How it starts

The opening of the file, as written. The whole thing — 65 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
  • 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.

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

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_analyze tool with:
  • rootPath: set to the workspace path
  • tool: 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

Read the full file on GitHub · 65 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. 1mo ago First seen · 65 lines · 822 tokens per session scan A 5a09c776a35a

Subscribe to this mod's changes

mcp-phpinsights codacy.instructions.md is an instructions file published in the GitHub repository salahmyn/mcp-phpinsights (0 stars, last pushed 4mo ago), licensed MIT. It adds 822 tokens to every session, about $0.0033 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 80% identical to aidevops codacy.instructions.md, differing in 69 lines, and is treated as a copy.

Related

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).

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,384 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

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.

denoland/deno · 3,077 tokens