sql-analyst

sql-analyst is a skill for Claude Code, Codex from librefang/librefang-registry. It costs 17 tokens per session (602 once invoked), scanned A, a copy of sql-analyst, MIT.

A SQL guide for writing, debugging, optimizing, and explaining database queries across common SQL systems.

In plain words
What is it for?
Use it to analyze data, design schemas, improve queries with execution plans, and work with PostgreSQL, MySQL, SQLite, or SQL Server.
Why use it?
It helps avoid slow queries, unclear joins, inefficient indexes, and mistakes caused by differences between SQL dialects.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

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 skills/librefang/librefang-registry/sql-analyst
Any agent
npx skills add librefang/librefang-registry --skill sql-analyst
Clone the repo
git clone --depth 1 https://github.com/librefang/librefang-registry

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for sql-analyst

README.md
[![agentmods](https://agentmods.dev/badge/skills/librefang/librefang-registry/sql-analyst.svg)](https://agentmods.dev/skills/librefang/librefang-registry/sql-analyst)
Your own site
<a href="https://agentmods.dev/skills/librefang/librefang-registry/sql-analyst"><img src="https://agentmods.dev/badge/skills/librefang/librefang-registry/sql-analyst.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 602 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 89% copy Near-identical to another mod 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.1 $0.00017 $0.00602
Opus 5 $0.00009 $0.00301
Sonnet 5 $0.00003 $0.00120
Haiku 4.5 $0.00002 $0.00060

Measured 2d ago against content hash 9b1a05ae1bc2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

sql-analyst 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.

Origin

This is a copy

89% identical to sql-analyst — 3 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.

skills/sql-analyst/SKILL.md · 48 lines

How it starts

The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SQL Query Expert

You are a SQL expert. You help users write, optimize, and debug SQL queries, design database schemas, and perform data analysis across PostgreSQL, MySQL, SQLite, and other SQL dialects.

Key Principles

  • Always clarify which SQL dialect is being used — syntax differs significantly between PostgreSQL, MySQL, SQLite, and SQL Server.
  • Write readable SQL: use consistent casing (uppercase keywords, lowercase identifiers), meaningful aliases, and proper indentation.
  • Prefer explicit JOIN syntax over implicit joins in the WHERE clause.
  • Always consider the query execution plan when optimizing — use EXPLAIN or EXPLAIN ANALYZE.

Query Optimization

  • Add indexes on columns used in WHERE, JOIN, ORDER BY, and GROUP BY clauses.
  • Avoid SELECT * in production queries — specify only the columns you need.
  • Use EXISTS instead of IN for subqueries when checking existence, especially with large result sets.
  • Avoid functions on indexed columns in WHERE clauses (e.g., WHERE YEAR(created_at) = 2025 prevents index use; use range conditions instead).
  • Use LIMIT and pagination for large result sets. Never return unbounded results to an application.
  • Consider CTEs (WITH clauses) for readability, but be aware that some databases materialize them (impacting performance).

Schema Design

  • Normalize to at least 3NF for transactional workloads. Denormalize deliberately for read-heavy analytics.
  • Use appropriate data types: TIMESTAMP WITH TIME ZONE for dates, NUMERIC/DECIMAL for money, UUID for distributed IDs.
  • Always add NOT NULL constraints unless the column genuinely needs to represent missing data.
  • Define foreign keys for referential integrity. Add ON DELETE behavior explicitly.
  • Include created_at and updated_at timestamp columns on all tables.

Analysis Patterns

  • Use window functions (ROW_NUMBER, RANK, LAG, LEAD, SUM OVER) for running totals, rankings, and comparisons.
  • Use GROUP BY with HAVING to filter aggregated results.
  • Use COALESCE and NULLIF to handle null values gracefully in calculations.

Read the full file on GitHub · 48 lines

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. 2d ago First seen · 48 lines · 17 tokens per session scan A 9b1a05ae1bc2

Subscribe to this mod's changes

sql-analyst is a skill published in the GitHub repository librefang/librefang-registry (11 stars, last pushed 12d ago), licensed MIT. It adds 17 tokens to every session and 602 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to sql-analyst, differing in 3 lines, and is treated as a copy.

Related

Other skills, from other repositories

postgresql-expert

Expert-level PostgreSQL database administration, advanced queries, performance tuning, and production operations. Use when the user mentions database, SQL, or performance, or when the task involves Advanced Data Types, Full-Text Search, Advanced Indexes, or Advanced Queries.

personamanagmentlayer/pcl · 56 tokens

database

Query and manage SQLite, PostgreSQL, and MySQL databases from the command line. Use when the user asks to run SQL queries, inspect database schemas, create or alter tables, import or export data, manage indexes, analyze query performance with EXPLAIN, back up or restore databases, or perform CRUD operations via…

bug-ops/zeph · 76 tokens

sql-expert

Expert-level SQL database design, querying, optimization, and administration across PostgreSQL, MySQL, and SQL Server. Use when the user mentions database, PostgreSQL, MySQL, or query optimization, or when the task involves Database Design, Advanced Queries, Indexes and Performance, or Transactions and Concurrency.

personamanagmentlayer/pcl · 66 tokens

snowflake-expert

Expert-level Snowflake data warehouse platform, virtual warehouses, data sharing, streams, tasks, and SQL optimization. Use when the user mentions data warehouse, SQL, analytics, or cloud, or when the task involves Architecture and Virtual Warehouses, Database Objects and Organization, Data Loading and Stages, or…

personamanagmentlayer/pcl · 69 tokens

postgresql-expert

Expert-level PostgreSQL database administration, advanced queries, performance tuning, and production operations.

itokun99/superspec-ai-workflow · 21 tokens

postgres-patterns

PostgreSQL database patterns for query optimization, schema design, indexing, and security. Quick reference for common patterns, index types, data types, and anti-pattern detection. Based on Supabase best practices.

affaan-m/ECC · 45 tokens