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 ajitpratap0/GoSQLX --skill sql-formattinggit clone --depth 1 https://github.com/ajitpratap0/GoSQLXWrote 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/ajitpratap0/gosqlx/sql-formatting)<a href="https://agentmods.dev/skills/ajitpratap0/gosqlx/sql-formatting"><img src="https://agentmods.dev/badge/skills/ajitpratap0/gosqlx/sql-formatting/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/ajitpratap0/gosqlx/sql-formatting"><img src="https://agentmods.dev/badge/skills/ajitpratap0/gosqlx/sql-formatting.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.00055 | $0.00585 |
| Opus 5.5 | $0.00022 | $0.00234 |
| Sonnet 5.5 | $0.00011 | $0.00117 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
sql-formatting 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 6d 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 formatting with GoSQLX
Input: $ARGUMENTS - a SQL string or a path to a .sql file.
Steps
- Get the SQL (read the file if a path was given).
- Call
format_sql(mcp__plugin_gosqlx_gosqlx__format_sql) with:sql(required)indent_size- integer 0–16, default 2.0puts each statement on one line. Clauses always start at column 0; larger values only indent nested blocks such as CREATE TABLE column listsuppercase_keywords-trueupper-cases all keywords (AND,IN,CASE, ...) but not data type names such asint. The defaultfalsestill upper-cases clause keywords (SELECT,FROM,WHERE, ...) and leaves others such asand/oras written; the MCP tool cannot lowercase keywordsadd_semicolon- defaultfalse
- If formatting fails, the SQL probably does not parse: call
validate_sqland report the error instead of guessing a fix. - Show the formatted SQL in a fenced
sqlblock. When the input was a file, write the result back only if the user asked you to change the file; otherwise show it.
Formatting is whitespace and keyword-case only - it must not change meaning. If the output appears to drop or alter anything (comments, hints, dialect syntax), say so and keep the original.
Fallback when the MCP tools are unavailable
gosqlx format query.sql # print formatted SQL (keywords uppercased by default)
gosqlx format --indent 4 query.sql
gosqlx format --uppercase=false query.sql # lowercase clause keywords (do not use --no-uppercase: it currently uppercases)
gosqlx format --check query.sql # exit non-zero if the file needs formatting
gosqlx format -i query.sql # rewrite in place - only when asked
echo "select a from b" | gosqlx format
Both upper-case clause keywords by default. For lowercase keywords use the CLI with --uppercase=false.
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.
- 6d ago First seen · 37 lines · 55 tokens per session scan A 450f16beb85a
sql-formatting is a skill published in the GitHub repository ajitpratap0/GoSQLX (120 stars, last pushed yesterday), licensed Apache-2.0. It adds 55 tokens to every session and 585 once invoked, about $0.0002 per session on Opus 5.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-10-22.
Other skills, from other repositories
gograph
Go repository intelligence for Claude Code. Use when reading, navigating, editing, reviewing, or refactoring a Go codebase. Exposes 64 query, analysis, and workflow capabilities through the local gograph MCP server, including bounded first-call exploration, AST-aware call graphs, blast-radius analysis, impact, and…
squix
Run SQL queries across databases (Postgres, MySQL, SQLite, etc.) via the squix CLI. Use for running named queries, exploring schema, or parameterized queries. Always use -f for non-interactive output.
golang-samber-hot
In-memory caching in Golang using samber/hot — eviction algorithms (LRU, LFU, TinyLFU, W-TinyLFU, S3FIFO, ARC, TwoQueue, SIEVE, FIFO), TTL, cache loaders, sharding, stale-while-revalidate, missing key caching, and Prometheus metrics. Apply when using or adopting samber/hot, when the codebase imports…
golang-database
Comprehensive guide for Go database access — parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context propagation, and migration tooling. Use when writing, reviewing, or debugging Golang code that interacts with PostgreSQL…
sq
Guides use of the sq CLI to query SQL databases and tabular files with SLQ (sq's jq-like query language) or native SQL, manage sources, choose output formats, and run inspect, diff, and table commands. Use when the user mentions sq, SLQ, wrangling CSV/Excel/JSON/DB data, cross-source joins, or command-line data…
go
Use when writing, reviewing, testing, or shipping Go code and HTTP services: idioms, %w error wrapping, goroutine/context/errgroup concurrency, net/http 1.22 routing, log/slog, project layout, table-driven tests, Go hardening. NOT language-agnostic threat modeling (that is secure-coding), NOT Dockerfile/CI shipping…