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/planetscale/claude-plugin/08-codebase-sqlcommenter-instrumentationnpx skills add planetscale/claude-plugin --skill 08-codebase-sqlcommenter-instrumentationgit clone --depth 1 https://github.com/planetscale/claude-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.00033 | $0.01055 |
| Opus 5 | $0.00016 | $0.00528 |
| Sonnet 5 | $0.00007 | $0.00211 |
| Haiku 4.5 | $0.00003 | $0.00105 |
Grade A, and why
planetscale-codebase-sqlcommenter-instrumentation 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.
This is a copy
100% identical to planetscale-codebase-sqlcommenter-instrumentation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase SQLCommenter instrumentation
Purpose
Inspect the application repository connected to PlanetScale and recommend the correct SQLCommenter-style instrumentation so PlanetScale Insights and Postgres Traffic Control can attribute queries to application code paths. Do not edit files or install dependencies without approval.
Repository inspection
Identify:
- Language and framework.
- ORM or query builder.
- Database adapter.
- Migration tool.
- Background job system.
- Routing framework.
- Deployment metadata source, such as git SHA or release ID.
- Existing SQL comments, query tags, tracing, OpenTelemetry, or database middleware.
- PlanetScale connection configuration.
- Whether the repository connects to Vitess, Postgres, or both.
Recommended package mapping
Use the most native maintained option for the detected stack.
Ruby on Rails / ActiveRecord
Preferred for PlanetScale tag compatibility:
activerecord-sql_commenterfrom PlanetScale when Rails query comments need SQLCommenter format for PlanetScale Query Insights.
Other options:
- Rails built-in query logs when sufficient and compatible with the target database/Insights behavior.
marginaliafor older Rails or when Basecamp-style ActiveRecord query attribution is already in use.sqlcommenter_railswhere the project already uses the OpenTelemetry SQLCommenter ecosystem.
Recommend tags:
applicationcontrolleractionjobrouterelease_sha
Laravel / PHP
Preferred:
spatie/laravel-sql-commenterfor SQLCommenter-format comments compatible with PlanetScale Query Insights.
Recommend tags:
applicationroutecontrolleractionjobqueuerelease_sha
Prisma / TypeScript / JavaScript
Preferred:
- Prisma’s first-party SQL comments packages when Prisma is detected:
@prisma/sqlcommenter@prisma/sqlcommenter-query-tags@prisma/sqlcommenter-trace-context
Note: PlanetScale’s Postgres query-tag docs may list Prisma as lacking official SQLCommenter support, but Prisma’s own current docs provide first-party SQLCommenter packages. Prefer current Prisma docs when Prisma is detected.
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 · 191 lines · 33 tokens per session scan A 9890331329f3
planetscale-codebase-sqlcommenter-instrumentation is a skill published in the GitHub repository planetscale/claude-plugin (4 stars, last pushed 2d ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,055 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to planetscale-codebase-sqlcommenter-instrumentation, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…