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/moki74/mysql-mcp/agents-mdgit clone --depth 1 https://github.com/moki74/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/instructions/moki74/mysql-mcp/agents-md)<a href="https://agentmods.dev/instructions/moki74/mysql-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/moki74/mysql-mcp/agents-md.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.00338 | $0.00338 |
| Opus 5 | $0.00169 | $0.00169 |
| Sonnet 5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
mysql-mcp AGENTS.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 3d 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.
What it actually says
AGENTS Development Guidelines
- This project uses MySQL MCP with the latest stable version of Node.js.
Feature & Code Changes
- For any new feature, fix, or enhancement:
- Update
DOCUMENTATIONS.mdfirst. - Update
README.mdif the change is user-facing. - Always increment the version number in
package.jsonafter the task is completed. - Add an entry to
CHANGELOG.mdfor every version change. - Update Last Updated
README.mdwith the current date and time and use formatYYYY-MM-DD HH:MM:SS - Update the total tools count if there is any addition or removal of tools in
DOCUMENTATIONS.mdorREADME.md - Every time you added a new tool or modify the existing tool or remove the tool, you must update in
mcp-server.tsfile.
- Update
Documentation Rules
- Do not create new documentation files.
- All documentation updates must be written to
DOCUMENTATIONS.md. - Keep documentation changes concise and include a datetime if applicable.
Versioning Rules
- Increment the version in
package.jsonwhen:- A new feature is added
- A bug is fixed
- Documentation is updated
- Any production code is modified
Testing & Cleanup
- Any temporary or test files created during development must be removed after testing is completed.
Publishing Rules
- Before publishing to npmjs:
- Ensure the
dist-tagis set tolatest - Verify the version number matches
CHANGELOG.md
- Ensure the
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.
- 3d ago First seen · 33 lines · 338 tokens per session scan A 46681eed44ce
mysql-mcp AGENTS.md is an instructions file published in the GitHub repository moki74/mysql-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 338 tokens to every session, about $0.0017 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
seekstone CLAUDE.md
Instructions for shaqmughal/seekstone, covering claude.md, what this repo is, commands, the harness itself (run after npm install) and architecture.
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core, parameterized queries, migration strategy.
pg-dash CLAUDE.md
Claude Code instructions for indiekitai/pg-dash, covering pg-dash claude.md, 项目结构, 构建与测试, 发版纪律（强制） and 发版检查清单（每次 npm publish 前必须按序执行）.
jdbc-driver CLAUDE.md
Claude Code instructions for keboola/jdbc-driver, covering claude.md, project overview, build & test commands, jdbc driver and vscode sqltools extension.
MCP-SqlServer CLAUDE.md
Claude Code instructions for Aron-Valenzuela/MCP-SqlServer, covering claude.md, project overview, setup (for each user), 1. install dependencies and 2. configure claude desktop.
plsql-intelligence AGENTS.md
Instructions for MuhDur/plsql-intelligence, covering agents.md — plsql-intelligence, founder constraints (plan.md §3, non-negotiable), plan rules to internalize (plan.md §4), rule 1 – absolute (do not ever violate this) and irreversible git & filesystem actions.