Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/JansenAnalytics/claudexnpx agentmods add skills/jansenanalytics/claudex/sql-queryWrote 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/jansenanalytics/claudex/sql-query)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/sql-query"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/sql-query.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.00027 | $0.00408 |
| Opus 5 | $0.00014 | $0.00204 |
| Sonnet 5 | $0.00005 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
sql-query 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 4d 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
sql-query
Build and execute complex SQL queries for analytics: joins, window functions, CTEs, aggregations, pivots.
When to Use
- Writing analytical queries with window functions, CTEs, or complex joins
- Building reports from databases
- Optimizing slow queries
- Transforming data with SQL
- Benchmarking query performance
Scripts
| Script | Purpose | Usage |
|---|---|---|
format-query.sh |
Format and validate SQL queries | bash scripts/format-query.sh [file.sql|-] |
suggest-indexes.sh |
Analyze queries and suggest indexes | bash scripts/suggest-indexes.sh <sqlite|postgres> <db> <query> |
benchmark.sh |
Benchmark query execution time | bash scripts/benchmark.sh <sqlite|postgres> <db> <query|file.sql> [runs] |
References
| File | Contents |
|---|---|
window-functions.md |
Window function patterns and examples |
cte-patterns.md |
Common Table Expression patterns |
optimization-guide.md |
Query optimization techniques |
analytical-templates.md |
Ready-to-use analytical query templates |
Examples
Format a query
echo "SELECT a,b FROM t WHERE x=1 GROUP BY a ORDER BY b" | bash scripts/format-query.sh -
Benchmark a query
bash scripts/benchmark.sh sqlite mydb.sqlite3 "SELECT count(*) FROM orders" 10
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.
- 4d ago First seen · 51 lines · 27 tokens per session scan A 8e3cf395ea66
sql-query is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 408 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-09-03.
Other skills, from other repositories
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.
mysql-expert
MySQL and MariaDB administration and development: InnoDB internals, indexing, query tuning, replication, and online schema change. Use when the user mentions MySQL, MariaDB, InnoDB, my.cnf, slow queries, EXPLAIN, binlog or replication lag, gtid, Percona or pt-online-schema-change, or when the task involves designing a…
dbt-expert
Expert-level dbt (data build tool), models, tests, documentation, incremental models, macros, and Jinja templating. Use when the user mentions analytics engineering, SQL, data transformation, Jinja, or testing, or when the task involves Project Structure and Configuration, Sources and Staging Models, Intermediate and…
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.
relational-database-design
Designs or reviews a relational database schema for a given domain. Covers table structure, normalization, indexes, constraints, and migration strategy. Invoked when the user asks to design a schema, review a database structure, or optimize a data model.
Database Schema Reviewer
Reviews database schemas for normalization issues, missing indexes, naming inconsistencies, and scalability risks.