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 skills/usrrname/cursorrules/mysqlnpx skills add usrrname/cursorrules --skill mysqlgit clone --depth 1 https://github.com/usrrname/cursorrulesWhat 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.00010 | $0.00364 |
| Opus 5 | $0.00005 | $0.00182 |
| Sonnet 5 | $0.00002 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
mysql 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 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.
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
MySQL Skill
Write efficient, secure MySQL queries and database schemas.
When to Use
- Designing database schemas
- Writing SQL queries
- Optimizing query performance
- Managing database migrations
Critical Rules
Schema Design
- Use appropriate data types
- Define primary keys on all tables
- Add indexes for frequently queried columns
- Use foreign keys for referential integrity
- Normalize to 3NF, denormalize when needed for performance
Query Writing
- Use parameterized queries (never string concatenation)
- SELECT only needed columns
- Use EXPLAIN to analyze query performance
- Avoid SELECT * in production
- Use JOINs appropriately
Security
- Never expose database credentials in code
- Use connection pooling
- Sanitize all user inputs
- Grant least privilege access
- Enable SSL/TLS for connections
Performance
- Index foreign keys
- Use EXPLAIN ANALYZE for optimization
- Batch inserts when possible
- Use transactions for multi-statement operations
- Monitor slow query log
Examples
Good
-- Parameterized query
SELECT id, name, email
FROM users
WHERE status = ? AND created_at > ?;
-- Proper indexing
CREATE INDEX idx_user_status ON users(status, created_at);
Bad
-- String concatenation (SQL injection risk)
SELECT * FROM users WHERE name = '$userInput';
-- Missing LIMIT on large tables
SELECT * FROM logs;
Related
/typescript- For database interface types/laravel- Laravel database patterns
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 · 76 lines · 10 tokens per session scan A e18783258f08
mysql is a skill published in the GitHub repository usrrname/cursorrules (10 stars, last pushed 4mo ago), licensed ISC. It adds 10 tokens to every session and 364 once invoked, about $0.0001 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
Release Notes Generation
Mandatory fast-mcp-telegram release workflow. Use when the user says release, merge and release, bump version, tag, gh release, PyPI publish, or Telegram version announcement.
sourcery-pr-cycle
Runs the PR creation and Sourcery AI review loop until merge-ready: open PR with gh, poll checks and comments, fix blocking issues, push, re-request review, repeat. Use when the user asks to create a PR, run the Sourcery cycle, address Sourcery review comments, or get a branch merge-ready after review.
feature-development
Feature development workflow for Telegram MCP projects. Use when implementing new features including research, planning, implementation, testing, and documentation.
telegram-patterns
Telegram-specific patterns and Telethon library usage.
Clean Up Docs Push
Code cleanup, docs update, and git push workflow.
Remove Old Logs
Remove log files older than 1 day from logs directory.