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 h4vzz/awesome-ai-agent-skills --skill sql-query-generationgit clone --depth 1 https://github.com/h4vzz/awesome-ai-agent-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/h4vzz/awesome-ai-agent-skills/sql-query-generation)<a href="https://agentmods.dev/skills/h4vzz/awesome-ai-agent-skills/sql-query-generation"><img src="https://agentmods.dev/badge/skills/h4vzz/awesome-ai-agent-skills/sql-query-generation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/h4vzz/awesome-ai-agent-skills/sql-query-generation"><img src="https://agentmods.dev/badge/skills/h4vzz/awesome-ai-agent-skills/sql-query-generation.svg" alt="Reviewed on agentmods" width="80" 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.00032 | $0.02157 |
| Opus 5 | $0.00016 | $0.01078 |
| Sonnet 5 | $0.00006 | $0.00431 |
| Haiku 4.5 | $0.00003 | $0.00216 |
Grade A, and why
sql-query-generation 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 10d 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
94% identical to sql-query-generation — 2 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SQL Query Generation
This skill enables an AI agent to translate natural language questions into correct, efficient SQL queries. The agent maps user intent to the appropriate query constructs — joins, aggregations, window functions, CTEs, and subqueries — while respecting the target database schema. It also analyzes query performance with EXPLAIN plans and recommends optimizations such as indexing, predicate pushdown, and query restructuring.
Workflow
-
Parse the natural language request. Extract the analytical intent: what metric is being asked for, which entities are involved, what filters apply, and how results should be ordered or grouped. Distinguish between requests for aggregated summaries versus row-level detail.
-
Map to the database schema. Identify the relevant tables and columns from the schema. Resolve ambiguous references (e.g., "sales" could mean the
orderstable or therevenuecolumn). Determine the join path between tables using foreign key relationships, avoiding unnecessary joins that inflate result sets. -
Select the appropriate query constructs. Choose between simple aggregation, window functions, CTEs, or subqueries based on complexity. Use CTEs for multi-step calculations to improve readability. Use window functions for running totals, rankings, and comparisons within partitions. Prefer explicit JOINs over implicit comma-separated joins.
-
Generate the SQL query. Write syntactically correct SQL with consistent formatting: uppercase keywords, lowercase identifiers, aliased tables, and indented clauses. Include comments for complex logic. Always specify column aliases for computed expressions.
-
Validate and optimize. Run EXPLAIN (or EXPLAIN ANALYZE) on the generated query to inspect the execution plan. Look for full table scans, hash joins on large tables, and sort operations on unindexed columns. Recommend indexes or query rewrites when the estimated cost is high.
-
Return results with explanation. Present the query alongside a plain-language explanation of what it does, the expected output format, and any assumptions made about the schema or data.
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.
- 10d ago First seen · 178 lines · 32 tokens per session scan A 0057cfecacc8
sql-query-generation is a skill published in the GitHub repository h4vzz/awesome-ai-agent-skills (34 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 2,157 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to sql-query-generation, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
sql-explainer
Paste a SQL query and get a plain English explanation of what it does.
drizzle
Skill "drizzle" from ashish7802/awesome-api-skills, covering drizzle orm skill, ecosystem graph preview, recommended next skills, quick start and production patterns.
mysql
Skill "mysql" from ashish7802/awesome-api-skills, covering mysql skill, ecosystem graph preview, recommended next skills, quick start and production patterns.
neon
Neon separates compute and storage, allowing instant database branching and autoscaling. For most Node.js applications, use the @neondatabase/serverless driver over standard pg to leverage WebSocket connections, which bypass serverless environment connection limits.
planetscale
PlanetScale provides branching workflows for MySQL. Install the @planetscale/database serverless driver to interact with it seamlessly over HTTP in Edge environments.
postgresql
Skill "postgresql" from ashish7802/awesome-api-skills, covering postgresql skill, ecosystem graph preview, recommended next skills, quick start and production patterns.