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 skills add neverinfamous/mysql-mcp --skill proxysqlgit clone --depth 1 https://github.com/neverinfamous/mysql-mcpWrote 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/proxysql)<a href="https://agentmods.dev/skills/neverinfamous/mysql-mcp/proxysql"><img src="https://agentmods.dev/badge/skills/neverinfamous/mysql-mcp/proxysql/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/proxysql"><img src="https://agentmods.dev/badge/skills/neverinfamous/mysql-mcp/proxysql.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00092 | $0.02099 |
| Opus 5 | $0.00046 | $0.01050 |
| Sonnet 5 | $0.00018 | $0.00420 |
| Haiku 4.5 | $0.00009 | $0.00210 |
Grade A, and why
proxysql 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 9d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ProxySQL Production Standards
ProxySQL is a high-performance MySQL proxy providing connection multiplexing, query routing, caching, and firewalling.
3.1 Architecture & Three-Layer Configuration
ProxySQL uses a strict multi-layer configuration system designed for dynamic, zero-downtime updates:
| Layer | Purpose | Mutability |
|---|---|---|
| MEMORY | Staging area (in-memory SQLite). Modifications here do NOT impact traffic. | Read/Write |
| RUNTIME | Active in-memory data structures used by worker threads. Dictates proxy behavior. | Read-only |
| DISK | Persistent SQLite DB (proxysql.db). Survives restarts. |
Via SAVE |
Configuration Workflow (CRITICAL):
-- Step 1: Make changes in MEMORY layer
INSERT INTO mysql_servers (hostgroup_id, hostname, port) VALUES (0, 'primary', 3306);
-- Step 2: Apply to RUNTIME (takes effect immediately)
LOAD MYSQL SERVERS TO RUNTIME;
-- Step 3: Persist to DISK (survives restarts)
SAVE MYSQL SERVERS TO DISK;
[!CAUTION] The #1 ProxySQL mistake: Modifying admin tables and assuming changes take effect. You MUST run
LOAD <MODULE> TO RUNTIMEfor changes to activate, andSAVE <MODULE> TO DISKfor persistence. Forgetting either step is the root cause of most ProxySQL configuration issues.
[!WARNING] Some global variables (
mysql-interfaces,mysql-threads) requireSAVE ... TO DISKand a full service restart —LOAD TO RUNTIMEalone is insufficient.
3.2 Connection Multiplexing
Multiplexing lets thousands of frontend clients share a small pool of backend connections, solving the C10K problem.
Anti-Patterns That Kill Multiplexing (result in "pinned" connections):
- Active transactions (
BEGINwithoutCOMMIT/ROLLBACK) - Temporary table creation
- User-defined variables (
SET @var) - Session-level state modifications (
SET FOREIGN_KEY_CHECKS) - Held prepared statements (binary protocol statement IDs are tied to specific backend connections)
- Long-running transactions
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.
- 9d ago First seen · 196 lines · 92 tokens per session scan A bb31ac875cd6
proxysql is a skill published in the GitHub repository neverinfamous/mysql-mcp (10 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 2,099 once invoked, about $0.0005 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
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.
supabase-node
Express/Hono with Supabase and Drizzle ORM.
nodejs-backend
Node.js backend patterns with Express/Fastify, repositories.
solr-extending
To build Solr plugins: SearchComponent, QParser, URP, DocTransformer.
spring-data-jpa
Use when generating JPA entities, repositories, queries, or anything touching the persistence layer. Covers entity conventions, N+1 prevention, projections, and query patterns.
spring-data-redis
Use when implementing caching, session storage, rate limiting, or any Redis integration. Covers cache-aside pattern, key naming, TTL strategy, and serialization config.