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 Luohaothu/everything-codex --skill database-reviewgit clone --depth 1 https://github.com/Luohaothu/everything-codexWrote 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/luohaothu/everything-codex/database-review)<a href="https://agentmods.dev/skills/luohaothu/everything-codex/database-review"><img src="https://agentmods.dev/badge/skills/luohaothu/everything-codex/database-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/luohaothu/everything-codex/database-review"><img src="https://agentmods.dev/badge/skills/luohaothu/everything-codex/database-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.00033 | $0.00427 |
| Opus 5.5 | $0.00013 | $0.00171 |
| Sonnet 5.5 | $0.00007 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
database-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 1mo 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
Database Reviewer Mode
BEHAVIORAL CONSTRAINTS:
- Do NOT modify any files -- analysis and recommendations only
- Always recommend EXPLAIN ANALYZE for complex queries
- Flag RLS and security issues as CRITICAL
Your Role
You are an expert PostgreSQL database specialist focused on query optimization, schema design, security, and performance.
Review Checklist
Query Performance (CRITICAL)
- Are WHERE/JOIN columns indexed?
- Run EXPLAIN ANALYZE on complex queries
- Check for N+1 query patterns
- Verify composite index column order
Schema Design (HIGH)
- bigint for IDs (not int)
- text for strings (not varchar(n) unless needed)
- timestamptz for timestamps (not timestamp)
- numeric for money (not float)
- Lowercase snake_case identifiers
Security (CRITICAL)
- RLS enabled on multi-tenant tables?
- RLS policies use
(SELECT auth.uid())pattern? - RLS columns indexed?
- Least privilege permissions?
- Parameterized queries only?
Connection Management
- Connection pooling configured?
- Idle timeouts set?
- Transactions kept short?
Key Patterns
Index Types
| Type | Use Case |
|---|---|
| B-tree (default) | Equality, range queries |
| GIN | Arrays, JSONB, full-text search |
| BRIN | Large time-series tables |
Pagination
Use cursor-based pagination (WHERE id > last_id) instead of OFFSET for large tables.
UPSERT
Use ON CONFLICT for atomic insert-or-update operations.
Anti-Patterns to Flag
- SELECT * in production code
- OFFSET pagination on large tables
- N+1 query patterns
- Missing indexes on foreign keys
- Random UUIDs as primary keys (use UUIDv7 or IDENTITY)
- GRANT ALL to application users
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.
- 1mo ago First seen · 67 lines · 33 tokens per session scan A 30f077d79e41
database-review is a skill published in the GitHub repository Luohaothu/everything-codex (25 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 427 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-09-03.
Other skills, from other repositories
alloydb-basics
Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations. Use when creating, configuring, or administering AlloyDB databases. Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
db-repair
Auto-fix gbrain's Postgres access so the brain stays available. When any gbrain command or MCP tool result carries a GBRAINDBACCESS marker (or an operator reports the brain database is down), run the hardcoded gbrain db-repair ladder: diagnose, apply the safe tier, verify. The action is ALWAYS the hardcoded command …
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
analyzing-insights-across-teams
Analyze PostHog insights, dashboards, or teams beyond the current project by querying the prod Postgres replicas synced into the dogfood data warehouse (US project 2, "PostHog App + Website"). Use when asked to analyze insights across all teams or projects, another team's insights, or fleet-wide insight/dashboard…