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/grantgit clone --depth 1 https://github.com/Efilkucf/mysql-mcp-pluginWrote 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/commands/efilkucf/mysql-mcp-plugin/grant)<a href="https://agentmods.dev/commands/efilkucf/mysql-mcp-plugin/grant"><img src="https://agentmods.dev/badge/commands/efilkucf/mysql-mcp-plugin/grant.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.00007 | $0.00396 |
| Opus 5 | $0.00003 | $0.00198 |
| Sonnet 5 | $0.00001 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade B, and why
grant 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 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.
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
Grant additional capabilities to a connection. Arguments: $ARGUMENTS.
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
If the connection name or capabilities are missing, run node <path> list to show
what exists, then ask. The capabilities are:
| Cap | Allows |
|---|---|
select |
SELECT, WITH … SELECT, TABLE, VALUES |
schema_read |
SHOW, DESCRIBE, EXPLAIN, USE |
insert |
INSERT, REPLACE, LOAD DATA |
update |
UPDATE |
delete |
DELETE |
ddl |
CREATE, ALTER, RENAME |
drop |
DROP, TRUNCATE |
admin |
GRANT, REVOKE, SET GLOBAL, user management, CALL |
Then run:
node <resolved-path> grant <name> <caps>
Two things to tell the user afterwards:
- Granting here only stops the plugin from refusing the operation. MySQL still
needs matching GRANTs — suggest
/mysql:test <name>to check. dropandadminare worth a moment's thought before granting. If they asked for either, confirm they meant it rather than granting silently.
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 · 42 lines · 7 tokens per session scan B ad3f7c52c0ff
grant is a command published in the GitHub repository Efilkucf/mysql-mcp-plugin (0 stars, last pushed 22d ago), licensed MIT. It adds 7 tokens to every session and 396 once invoked, about $0.0000 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
review-renovate
Review and merge renovate PRs with automerge configuration updates.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
plan-regression-tests
Plan regression tests for existing code with it.skip statements.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
ingest
Manually add knowledge to the Weaviate store.