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 commands/efilkucf/mysql-mcp-plugin/importgit clone --depth 1 https://github.com/Efilkucf/mysql-mcp-pluginWhat 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.00015 | $0.00386 |
| Opus 5 | $0.00008 | $0.00193 |
| Sonnet 5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade B, and why
import scanned grade B with 1 finding 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
|| find ~/.claude/plugins -name cli.js -path '*mysql*' -not -path '*/node_modules/*' 2>/dev/null | head -1 What it actually says
Migrate connections from the old env-var setup into the plugin's config.
Resolve the CLI path:
ls "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" 2>/dev/null \
|| find ~/.claude/plugins -name cli.js -path '*mysql*' -not -path '*/node_modules/*' 2>/dev/null | head -1
First do a dry run, which reports what it found without changing anything:
node <resolved-path> import
Show the user which connections and which ~/.claude.json scopes it found, then
confirm before running:
node <resolved-path> import --yes
Two things to explain up front:
-
Everything imports read-only (
select,schema_read) regardless of what the old config could do. The previous setup granted unrestricted write access to every connection, and migration deliberately does not carry that forward. Widening is an explicit/mysql:grant. -
~/.claude.jsonis not edited. The command prints whichenvblocks to delete, and the user does it once the new setup is confirmed working. That file holds unrelated settings, and leaving the old entries in place means there is a working fallback while they verify.
Afterwards, walk them through /mysql:test <name> for each imported connection.
Connections on 127.0.0.1 will only connect while their tunnel or port-forward is
running — a good moment to suggest converting those to an ssh block via
/mysql:add --force, so the plugin opens the tunnel itself.
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.
- 2d ago First seen · 44 lines · 15 tokens per session scan B d12e00d1243f
import is a command published in the GitHub repository Efilkucf/mysql-mcp-plugin (0 stars, last pushed 20d ago), licensed MIT. It adds 15 tokens to every session and 386 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.