PlanetScale Skills is a collection of markdown instructions that turns a coding agent into a reviewer and operator for PlanetScale databases, which are managed databases organized around branches and controlled schema changes. Database teams use it to audit configuration and query behavior, produce evidence-backed reports, apply approved changes, and automate monitoring through PlanetScale’s own workflows.
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 skills add planetscale/skills --skill planetscale-best-practices-matrixgit clone --depth 1 https://github.com/planetscale/skillsWrote 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/skills/planetscale/skills/planetscale-best-practices-matrix)<a href="https://agentmods.dev/skills/planetscale/skills/planetscale-best-practices-matrix"><img src="https://agentmods.dev/badge/skills/planetscale/skills/planetscale-best-practices-matrix.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.1 | $0.00031 | $0.01065 |
| Opus 5 | $0.00015 | $0.00532 |
| Sonnet 5 | $0.00006 | $0.00213 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
planetscale-best-practices-matrix 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- planetscale-best-practices-matrix — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Best-practices matrix
Purpose
Map database findings to recommended PlanetScale features. Use this to ensure the assessment does not miss major safety and operational surfaces.
Cross-engine recommendations
Query Insights
Recommend for every production database:
- Review slow, expensive, high-frequency, and erroring query patterns.
- For Postgres, sort Insights by CPU (
sort=cpuTimeon the Insights API) when diagnosing CPU pressure. - For sharded Vitess, review vindex usage per query pattern and the usage trend after index or routing changes.
- Correlate regressions with deploys.
- Use tags/comments to map queries back to code.
- Use tag filtering/navigation in Query Insights: the tags API
(
insights/tags,insights/tags/summaries) on both engines, plustag:key:valuefiltering and per-execution tag drill-down in the Vitess dashboard. - Use anomalies as alert and automation inputs.
Webhooks
Recommend for operational events:
- Anomalies.
- Storage pressure.
- Branch readiness/sleeping.
- Primary promotion.
- Maintenance.
- Schema recommendations where available.
- Deploy request lifecycle for Vitess.
MCP and agents
Recommend:
- Use insights-only MCP for most autonomous analysis.
- Use full MCP only with narrow scopes and read-only default.
- Put database targeting and safety rules in
AGENTS.md. - Agents generate PRs/issues/change plans; humans approve database changes.
SQLCommenter / query tags
Recommend:
- Add framework-native SQLCommenter-compatible instrumentation.
- Use low-cardinality tags.
- Include application, service, route/job, feature, source, and release SHA.
- Avoid PII and unbounded IDs.
Schema recommendation workflow
Recommend:
- Triage open recommendations.
- Correlate with code and Insights.
- Convert into migrations or branch changes.
- Test before production.
- Apply only through approved workflow.
Vitess-specific recommendations
Safe migrations
Recommend for production branches and staging branches that accept deploy requests.
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 · 174 lines · 31 tokens per session scan A e7db5b5ecf11
planetscale-best-practices-matrix is a skill published in the GitHub repository planetscale/skills (126 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 1,065 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
alloydb-basics
Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations. Use when creating, configuring, or administering AlloyDB databases. Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
db-repair
Auto-fix gbrain's Postgres access so the brain stays available. When any gbrain command or MCP tool result carries a GBRAINDBACCESS marker (or an operator reports the brain database is down), run the hardcoded gbrain db-repair ladder: diagnose, apply the safe tier, verify. The action is ALWAYS the hardcoded command …
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.
analyzing-insights-across-teams
Analyze PostHog insights, dashboards, or teams beyond the current project by querying the prod Postgres replicas synced into the dogfood data warehouse (US project 2, "PostHog App + Website"). Use when asked to analyze insights across all teams or projects, another team's insights, or fleet-wide insight/dashboard…