Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/neverinfamous/mysql-mcpnpx agentmods add skills/neverinfamous/mysql-mcp/mysql-mcp-infrastructureWrote 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/skills/neverinfamous/mysql-mcp/mysql-mcp-infrastructure)<a href="https://agentmods.dev/skills/neverinfamous/mysql-mcp/mysql-mcp-infrastructure"><img src="https://agentmods.dev/badge/skills/neverinfamous/mysql-mcp/mysql-mcp-infrastructure/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/skills/neverinfamous/mysql-mcp/mysql-mcp-infrastructure"><img src="https://agentmods.dev/badge/skills/neverinfamous/mysql-mcp/mysql-mcp-infrastructure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 49 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 50 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 58 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 68 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00055 | $0.01203 |
| Opus 5 | $0.00028 | $0.00602 |
| Sonnet 5 | $0.00011 | $0.00241 |
| Haiku 4.5 | $0.00006 | $0.00120 |
Grade A, and why
mysql-mcp-infrastructure 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 10d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MySQL MCP Infrastructure & Examples Guide
The mysql-mcp repository contains complex, multi-node database ecosystems for both advanced E2E testing and user examples. When an AI agent is asked to orchestrate, set up, or troubleshoot these environments, they MUST follow these specific procedures.
1. Core Test Ecosystem (test-server)
The core test ecosystem is derived from the master adamic unified database ecosystem. It includes a 3-node InnoDB cluster, MySQL Router, ProxySQL, and a full observability stack (Datadog, Prometheus, Grafana, Dozzle).
To Recreate the Ecosystem: If the test infrastructure breaks, has port conflicts, or needs to be completely wiped and re-created:
⚠️ SAFETY GATE: This script permanently destroys all containers and data in the test ecosystem. You MUST obtain explicit user confirmation (e.g., "yes, destroy everything") before running this command. Never infer intent.
# Natively on Windows (via PowerShell or cmd)
node test-server/infrastructure/scripts/recreate-ecosystem.mjs
Note: This will completely tear down the containers, initialize the InnoDB cluster, join secondary nodes, and run the
reset-database.mjsseed script.
To Re-seed Data (Without Teardown): If the cluster is healthy but the data is dirty:
node test-server/infrastructure/scripts/reset-database.mjs
To Recover a Broken Cluster (Quorum Loss):
If the InnoDB cluster loses quorum or the primary is stuck in super_read_only mode:
node test-server/infrastructure/scripts/heal-primary.mjs
2. Setting Up Examples
The repository provides standalone example stacks. Always copy the .env.example to .env before bringing up the stacks.
Basic MySQL + Datadog Example
Located in examples/basic-mysql-datadog. This is a lightweight stack demonstrating Datadog observability.
cd examples/basic-mysql-datadog
cp .env.example .env
# Edit .env with your DD_API_KEY
docker compose up -d
Enterprise HA MySQL Example
Located in examples/enterprise-ha-mysql. This is a heavy stack demonstrating a fully configured InnoDB Cluster with ProxySQL.
cd examples/enterprise-ha-mysql
cp .env.example .env
docker compose up -d
# Wait for containers to be healthy, then run the initialization script:
bash init-cluster.sh
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.
- 10d ago First seen · 93 lines · 55 tokens per session scan A af69ce7b51ab
mysql-mcp-infrastructure is a skill published in the GitHub repository neverinfamous/mysql-mcp (10 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 1,203 once invoked, about $0.0003 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 skills, from other repositories
Drizzle ORM Testing
Testing patterns for Drizzle ORM covering migration testing, query builder testing, transaction testing, and database integration testing with PostgreSQL, SQLite, and MySQL.
dory
Use Dory as the official AI-native SQL workspace for agents. Use when the user asks to inspect or analyze databases, explore unknown schemas, debug data issues, run read-only SQL through Dory MCP, manage Dory Agent Runs, create or update SQL workspace tabs, work with saved queries, preserve query results, or hand SQL…
misata
Generate realistic multi-table test data, seed a development database, or build fixtures whose joins and totals actually hold. Use when the user needs test data, sample data, demo data, seed data, fixtures, a populated dev/staging database, or a relational dataset shaped to specific numbers (a revenue curve, a churn…
testing-a-datavault4dbt-project
Adds Data Vault 2 technical tests to a datavault4dbt project — hashkey uniqueness and not-null, link-to-hub referential integrity, and satellite key+load-date uniqueness — as dbt soft-constraint tests in YAML. Use when adding or reviewing tests for hubs, links, or satellites, or validating raw vault integrity.
smoke-test-database
Quick Reference - Load this first for fast context (3KB).
test-data-strategy
Get realistic test data in an organization where production data cannot be copied - synthesis, subsetting, masking with referential integrity preserved, and fixtures for the awkward edge cases that only real systems produce. Use when tests need data you do not have, when verification is blocked because no usable…