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 medy-gribkov/arcana --skill postgres-advancedgit clone --depth 1 https://github.com/medy-gribkov/arcanaWrote 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/medy-gribkov/arcana/postgres-advanced)<a href="https://agentmods.dev/skills/medy-gribkov/arcana/postgres-advanced"><img src="https://agentmods.dev/badge/skills/medy-gribkov/arcana/postgres-advanced.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.1 | $0.00037 | $0.02596 |
| Opus 5 | $0.00018 | $0.01298 |
| Sonnet 5 | $0.00007 | $0.00519 |
| Haiku 4.5 | $0.00004 | $0.00260 |
Grade A, and why
postgres-advanced 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 7d 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 — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Advanced PostgreSQL Operations
Expert-level PostgreSQL patterns for production systems: analytical queries, JSON handling, search optimization, and performance tuning.
Window Functions
Perform calculations across row sets without collapsing results.
BAD: Self-join for ranking
-- Inefficient, creates cartesian product
SELECT e1.name, e1.salary, COUNT(e2.salary) as rank
FROM employees e1
LEFT JOIN employees e2 ON e1.salary <= e2.salary
GROUP BY e1.name, e1.salary;
GOOD: ROW_NUMBER and RANK
-- Efficient window function
SELECT
name,
salary,
department,
ROW_NUMBER() OVER (PARTITION BY department ORDER BY salary DESC) as row_num,
RANK() OVER (PARTITION BY department ORDER BY salary DESC) as rank,
DENSE_RANK() OVER (PARTITION BY department ORDER BY salary DESC) as dense_rank
FROM employees;
BAD: Subquery for previous value
-- Poor performance, scalar subquery per row
SELECT
date,
revenue,
(SELECT revenue FROM sales s2
WHERE s2.date < s1.date
ORDER BY date DESC LIMIT 1) as prev_revenue
FROM sales s1;
GOOD: LAG/LEAD for row comparison
-- Single scan with window function
SELECT
date,
revenue,
LAG(revenue, 1) OVER (ORDER BY date) as prev_revenue,
LEAD(revenue, 1) OVER (ORDER BY date) as next_revenue,
revenue - LAG(revenue, 1) OVER (ORDER BY date) as revenue_change
FROM sales;
Running totals and moving averages
-- Cumulative sum and 7-day moving average
SELECT
date,
amount,
SUM(amount) OVER (ORDER BY date ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW) as running_total,
AVG(amount) OVER (ORDER BY date ROWS BETWEEN 6 PRECEDING AND CURRENT ROW) as moving_avg_7d,
FIRST_VALUE(amount) OVER (ORDER BY date) as first_amount,
LAST_VALUE(amount) OVER (ORDER BY date ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING) as last_amount
FROM transactions;
Common Table Expressions (CTEs)
BAD: Nested subqueries
-- Unreadable, hard to maintain
SELECT * FROM (
SELECT * FROM (
SELECT user_id, COUNT(*) as cnt
FROM orders
GROUP BY user_id
) t1 WHERE cnt > 5
) t2 JOIN users ON t2.user_id = users.id;
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.
- 7d ago First seen · 389 lines · 37 tokens per session scan A 02af5b41aa15
postgres-advanced is a skill published in the GitHub repository medy-gribkov/arcana (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 2,596 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
database-patterns
DB schema design and query tuning: normalization, indexing, N+1, transactions, EXPLAIN. Triggers: schema, index, slow query, N+1, PostgreSQL, MySQL, EXPLAIN, deadlock, query plan.
database-expert
Advanced database design and administration for PostgreSQL, MongoDB, and Redis. Use when designing schemas, optimizing queries, managing database performance, or implementing data patterns.
api-baas-neon
Serverless PostgreSQL with branching, autoscaling, and edge-compatible driver.
pg-migration
PostgreSQL schema migration safety reviewer and DDL generator. ALWAYS use when writing, reviewing, or planning PostgreSQL schema changes — ALTER TABLE, CREATE/DROP INDEX, column type changes, constraint additions, RLS policy changes, or any DDL touching production tables. Covers lock-level analysis, CREATE INDEX…
api-database-postgresql
Direct PostgreSQL access with node-postgres (pg) -- connection pools, parameterized queries, transactions, streaming, LISTEN/NOTIFY, error handling.
api-database-vercel-postgres
Serverless PostgreSQL on Vercel with edge-compatible SDK.