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/call518/mcp-mysql-ops/copilot-instructionsgit clone --depth 1 https://github.com/call518/MCP-MySQL-OpsWrote 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/call518/mcp-mysql-ops/copilot-instructions)<a href="https://agentmods.dev/instructions/call518/mcp-mysql-ops/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/call518/mcp-mysql-ops/copilot-instructions.svg" alt="Measured on agentmods" 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 | $0.01958 | $0.01958 |
| Opus 5 | $0.00979 | $0.00979 |
| Sonnet 5 | $0.00392 | $0.00392 |
| Haiku 4.5 | $0.00196 | $0.00196 |
Grade A, and why
MCP-MySQL-Ops copilot-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP MySQL Operations Server - AI Coding Agent Instructions
Architecture Overview
This is a Model Context Protocol (MCP) server built with FastMCP that provides MySQL database monitoring and operations through natural language queries. The server acts as a safe, read-only bridge between AI assistants and MySQL databases.
Core Components
mcp_main.py: Main MCP server with 19+@mcp.tool()decorated functionsfunctions.py: Database connection layer usingaiomysqlwith multi-database supportversion_compat.py: MySQL 5.7.9+ and 8.0+ version detection and adaptive feature handling (MIN_SUPPORTED_VERSION = 5.7.9is enforced viaensure_min_supported_version)prompt_template.md: Comprehensive prompt definitions loaded via@mcp.prompt()decorators- Docker stack: MySQL + MCP server + MCPO proxy + Open WebUI integration
Key Patterns
Multi-Database Architecture: All tools accept optional database_name parameter to target specific databases while maintaining a default connection database from MYSQL_DATABASE env var.
Performance Schema Integration: Core functionality leverages MySQL's Performance Schema and Information Schema. Tools automatically detect available features and adapt accordingly.
Version-Aware Tools: Use version_compat.py for MySQL 5.7.9+/8.0+ compatibility. Tools auto-adapt features based on detected version, and ensure_min_supported_version() raises UnsupportedMySQLVersionError for servers older than 5.7.9 (which lack performance_schema.processlist). MySQL 8.0+ recommended for enhanced capabilities.
Tool Structure: Each MCP tool follows this pattern:
@mcp.tool()
async def get_something(limit: int = 20, database_name: str = None) -> str:
"""Detailed docstring with [Tool Purpose], [Exact Functionality], [Required Use Cases], [Strictly Prohibited Use Cases]"""
try:
# Validate inputs (limit constraints: max 1-100)
# Execute queries via functions.py
# Return formatted table data
except Exception as e:
logger.error(f"Failed to...: {e}")
return f"Error: {str(e)}"
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.
- 5d ago First seen · 189 lines · 1,958 tokens per session scan A 77235ddc6a57
MCP-MySQL-Ops copilot-instructions.md is an instructions file published in the GitHub repository call518/MCP-MySQL-Ops (2 stars, last pushed 1mo ago), licensed MIT. It adds 1,958 tokens to every session, about $0.0098 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.
Other instructions, from other repositories
mysql-mcp copilot-instructions.md
Copilot instructions for neverinfamous/mysql-mcp, covering mysql-mcp — copilot code review context, enforce core architecture rules, review session context, uphold coding standards and standardize file naming.
deepsql CLAUDE.md
Claude Code instructions for DeepSQLAI/deepsql, covering claude.md — dba agent, project overview, development commands, backend (spring boot) and frontend (react + vite).
bigquery-mcp CLAUDE.md
Instructions for pvoo/bigquery-mcp, covering claude.md, project overview, development commands, setup (recommended approach) and or manual setup.
deepsql AGENTS.md
AGENTS.md instructions for DeepSQLAI/deepsql, covering agents.md, project overview, commands, backend and frontend.
db-mcp-server CLAUDE.md
Instructions for vika2603/db-mcp-server, covering claude.md, build and development commands, architecture, layer structure and key design patterns.
mcp-database-server CLAUDE.md
Instructions for ahmetbarut/mcp-database-server, covering claude.md, project overview, commands, architecture and core flow.