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.
git 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/commands/ajitpratap0/gosqlx/lint)<a href="https://agentmods.dev/commands/ajitpratap0/gosqlx/lint"><img src="https://agentmods.dev/badge/commands/ajitpratap0/gosqlx/lint/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/commands/ajitpratap0/gosqlx/lint"><img src="https://agentmods.dev/badge/commands/ajitpratap0/gosqlx/lint.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.00020 | $0.00214 |
| Opus 5.5 | $0.00008 | $0.00086 |
| Sonnet 5.5 | $0.00004 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
lint 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 yesterday.
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
Lint this SQL with GoSQLX: $ARGUMENTS
If the argument is a path to an existing file, read it and use its contents; otherwise treat the argument as SQL text. If it is empty, ask for the SQL.
Call the lint_sql MCP tool. Group the violations by rule ID, show each offending line with its line/column, and give the fix; note which rules gosqlx lint --auto-fix can fix (L001, L002, L003, L007, L010). Use the sql-linting skill for rule explanations. If the MCP server is unavailable, run gosqlx lint via Bash. Do not modify any file unless asked.
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.
- yesterday First seen · 12 lines · 20 tokens per session scan A c374d23d40e6
lint is a command published in the GitHub repository ajitpratap0/GoSQLX (120 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 214 once invoked, about $0.0001 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 commands, from other repositories
db-setup
Configure the local database connection.
migrate-db
Rebuilds the local database from scratch for development.
astro-dev
Command "astro-dev" from MadAppGang/dingo, covering astro development orchestration workflow, initialization (before phase 1), step 0.1: validate working directory, step 0.2: create session folder and step 0.3: ensure .gitignore exists.
astro-fix
Command "astro-fix" from MadAppGang/dingo, covering astro visual fix orchestration workflow, initialization (before phase 1), step 0.1: validate working directory, step 0.2: create session folder and step 0.3: ensure .gitignore exists.
setup
Interactive setup for Go LSP development environment.
fix
Auto-fix linting, formatting, and common issues.