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 woliveiras/geremmyas --skill postgres-query-reviewgit clone --depth 1 https://github.com/woliveiras/geremmyasWrote 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/woliveiras/geremmyas/postgres-query-review)<a href="https://agentmods.dev/skills/woliveiras/geremmyas/postgres-query-review"><img src="https://agentmods.dev/badge/skills/woliveiras/geremmyas/postgres-query-review/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/woliveiras/geremmyas/postgres-query-review"><img src="https://agentmods.dev/badge/skills/woliveiras/geremmyas/postgres-query-review.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.00048 | $0.00372 |
| Opus 5 | $0.00024 | $0.00186 |
| Sonnet 5 | $0.00010 | $0.00074 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
postgres-query-review 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.
What it actually says
Postgres Query Review
Review PostgreSQL changes through correctness, plan shape, and operational risk.
Process
- Identify the query or migration, expected data volume, critical path, and latency or safety target.
- Check correctness first: joins, filters, null handling, constraints, transactions, and isolation assumptions.
- Inspect indexes used by
WHERE,JOIN,ORDER BY, uniqueness, and policy predicates. - Request or read
EXPLAIN/EXPLAIN ANALYZEfor important queries on realistic data. - For migrations, review locks, table rewrites, backfills, concurrent index creation, and rollback strategy.
- Check connection pool impact and transaction duration.
- Propose the smallest change that addresses the measured issue.
Rules
- Do not add indexes without a query pattern and expected benefit.
- Do not use production
EXPLAIN ANALYZEon dangerous writes. - Do not hold transactions open across network calls or user interaction.
- Run destructive migrations or large rewrites autonomously only on a verified
local, disposable, or test database with rollback or recreation, prefixing
guarded commands with
GEREMMYAS_TARGET=local,test, ordisposable. Production execution requires explicit user authorization; an ambiguous database is protected.
Output
- Correctness findings
- Plan/index observations
- Migration/lock risk
- Recommended SQL or migration change
- Verification command or metric
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 · 45 lines · 48 tokens per session scan A bf8b92d7b4de
postgres-query-review is a skill published in the GitHub repository woliveiras/geremmyas (10 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 372 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
tom-lane-perspective
A perspective skill based on research about Tom Lane, a PostgreSQL core maintainer. PostgreSQL is an open-source database; the skill applies his documented ways of thinking to project governance, patch review, and debugging decisions.
postgresql
PostgreSQL schema design, query optimization, indexing, and administration. Use when writing schemas, queries, migrations, or mentions PostgreSQL, Postgres, JSONB, partitioning, RLS, CTEs, window functions, EXPLAIN ANALYZE, or connection pooling.
ia-postgresql
PostgreSQL schema design, query optimization, indexing, and administration. Use when working with PostgreSQL, JSONB, partitioning, RLS, CTEs, window functions, or EXPLAIN ANALYZE.
sqlike
Check SQL with sqlike — deterministic static analysis (validity, anti-patterns, rewrites, index advice) and query-equivalence verification. Use whenever you write, edit, review, or rewrite a SQL query, or need to prove two queries return the same results. Requires the sqlike MCP server (@sqlike/mcp) or the sqlike CLI…
postgresql-rails-analyzer
Comprehensive PostgreSQL configuration and usage analysis for Rails applications. Use when Claude Code needs to analyze a Rails codebase for database performance issues, optimization opportunities, or best practice violations. Detects N+1 queries, missing indexes, suboptimal database configurations, anti-patterns, and…
agent-database-reviewer
PostgreSQL database specialist for query optimization, schema design, security, and performance. Use PROACTIVELY when writing SQL, creating migrations, designing schemas, or troubleshooting database performance. Incorporates Supabase best practices.