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 agentmods add skills/datatorag/mcp-gateway/db-querynpx skills add datatorag/mcp-gateway --skill db-querygit clone --depth 1 https://github.com/datatorag/mcp-gatewayWrote 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/datatorag/mcp-gateway/db-query)<a href="https://agentmods.dev/skills/datatorag/mcp-gateway/db-query"><img src="https://agentmods.dev/badge/skills/datatorag/mcp-gateway/db-query.svg" alt="Measured on agentmods" 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 | $0.00060 | $0.01777 |
| Opus 5 | $0.00030 | $0.00889 |
| Sonnet 5 | $0.00012 | $0.00355 |
| Haiku 4.5 | $0.00006 | $0.00178 |
Grade A, and why
db-query 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DB Query — Local + Production
Query the DataToRAG Postgres database without hard-coding any infrastructure details in this file. This skill lives in a public repo, so it deliberately uses placeholders and references private memory for the real values.
Production runs on Neon serverless Postgres, queried through the Neon MCP (plugin: neon@claude-plugins-official) — NOT via SSH into a docker Postgres on the gateway host. The old docker-on-gateway path is retired; the gateway host no longer runs the production database. Local dev still uses a docker Postgres.
Where the actual values come from
Memory files hold the operational details:
reference_neon_database.md— production Neon project id + region (query via Neon MCP)reference_gateway_dev_port.md— local dev server port (separate from DB)- (Postgres user/database name for local dev is
datatoragmcp/datatoragmcp; non-sensitive — the password is in the container's env, not this file)
If the agent doesn't have the reference_neon_database.md entry, run the Neon MCP's list_projects to find the production project (its name/id are in memory, not here), or ask the user. If the Neon MCP isn't connected, install it: claude plugin install neon@claude-plugins-official --scope user, then /reload-plugins and authenticate (OAuth).
Local (dev)
The local Postgres runs inside the dev docker-compose stack started from docker/.
1. Find the local postgres container:
docker ps --filter 'name=postgres' --format '{{.Names}}'
Expected: a container name like docker-postgres-1 or similar.
2. Run a query:
docker exec -it <container> psql -U datatoragmcp -d datatoragmcp -c "SELECT ..."
3. Or open an interactive psql session:
docker exec -it <container> psql -U datatoragmcp -d datatoragmcp
4. Pipe multi-line SQL via stdin:
cat <<'SQL' | docker exec -i <container> psql -U datatoragmcp -d datatoragmcp
SELECT ...
WHERE ...;
SQL
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.
- 4d ago First seen · 209 lines · 60 tokens per session scan A 465b3eb7674b
db-query is a skill published in the GitHub repository datatorag/mcp-gateway (3 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 1,777 once invoked, about $0.0003 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
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.
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 …
amazon aurora dsql
Deprecated compatibility redirect for Aurora DSQL guidance. Use when a request concerns DSQL, Aurora DSQL, distributed SQL, DSQL schemas, migrations, queries, authentication, performance, or application development.
claimable-postgres
Provision instant temporary Postgres databases via Claimable Postgres by Neon (neon.new) with no login, signup, or credit card. Supports REST API, CLI, and SDK. Use when users ask for a quick Postgres environment, a throwaway DATABASEURL for prototyping/tests, or "just give me a DB now". Triggers include: "quick…
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…
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…