cursor-rule

A rule that protects MySQL command-line operations that write data, change database structures, or can destroy data.

In plain words
What is it for?
Use it when working with mysql-cli commands containing write, DDL (database-structure changes), or confirmation flags such as --yes.
Why use it?
It prevents these higher-risk commands from running before a person reviews and approves the exact command and its impact.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/allenmuu/mysql-cli/cursor-rule
Clone the repo
git clone --depth 1 https://github.com/AllenMuu/mysql-cli
Per session 172 This file is loaded in full into every session.
When invoked 172 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00172 $0.00172
Opus 5 $0.00086 $0.00086
Sonnet 5 $0.00034 $0.00034
Haiku 4.5 $0.00017 $0.00017

Measured yesterday against content hash 508f1e857dae, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursor-rule 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 yesterday.

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.

internal/agentsetup/templates/cursor-rule.mdc · 19 lines

What it actually says

mysql-cli 写操作守卫

mysql-cli 默认只读。若命令行包含 --write--ddl--yes 中的任意一个,即为写/破坏性操作。

执行前必须

  1. 停下来,向用户展示完整命令与影响范围;
  2. 明确请求人工确认;
  3. 未获明确批准前不得执行。

--yes 是“标记破坏性操作”,不是豁免确认——不得用 --yes 绕过本规则。

完整安全模型见 skills/mysql-shared/SKILL.md 的 Security Model 段。

Changes

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.

  1. yesterday First seen · 19 lines · 172 tokens per session scan A 508f1e857dae

Subscribe to this mod's changes

cursor-rule is a cursor rule published in the GitHub repository AllenMuu/mysql-cli (2 stars, last pushed 20d ago), licensed MIT. It adds 172 tokens to every session, about $0.0009 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.