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 tallclub/matimo --skill postgresgit clone --depth 1 https://github.com/tallclub/matimoWrote 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/tallclub/matimo/postgres)<a href="https://agentmods.dev/skills/tallclub/matimo/postgres"><img src="https://agentmods.dev/badge/skills/tallclub/matimo/postgres/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/tallclub/matimo/postgres"><img src="https://agentmods.dev/badge/skills/tallclub/matimo/postgres.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00026 | $0.01923 |
| Opus 5.5 | $0.00010 | $0.00769 |
| Sonnet 5.5 | $0.00005 | $0.00385 |
| Haiku 4.5 | $0.00003 | $0.00192 |
Grade A, and why
postgres 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 2mo 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PostgreSQL
This skill teaches you how to safely execute SQL queries against a PostgreSQL database using Matimo tools, with emphasis on parameterized queries, schema awareness, and safe patterns.
Tools You Will Use
| Tool | Purpose |
|---|---|
postgres-execute-sql |
Execute any SQL statement against a connected Postgres database |
Executing a Query
Use postgres-execute-sql to run SQL statements. The tool supports parameterized queries for safety.
Parameters
| Parameter | Type | Description |
|---|---|---|
sql |
string | SQL statement to execute. Use $1, $2, etc. for parameterized values |
params |
array | Optional array of parameter values (matched by position to $1, $2, etc.) |
schema |
string | Optional schema name for table qualification |
Critical: Always Use Parameterized Queries
NEVER interpolate user-provided values directly into SQL strings. Always use $1, $2 placeholders.
// ✅ SAFE — parameterized
{
"sql": "SELECT * FROM users WHERE email = $1",
"params": ["[email protected]"]
}
// ❌ DANGEROUS — SQL injection risk
{
"sql": "SELECT * FROM users WHERE email = '[email protected]'"
}
This prevents SQL injection attacks regardless of the input content.
Read Operations
Select with Parameters
{
"sql": "SELECT id, name, email FROM users WHERE id = $1",
"params": [42]
}
Select with Multiple Conditions
{
"sql": "SELECT * FROM orders WHERE status = $1 AND created_at > $2",
"params": ["pending", "2025-01-01"]
}
Count Records
{
"sql": "SELECT count(*) as total FROM users WHERE active = $1",
"params": [true]
}
Pagination Pattern
{
"sql": "SELECT id, name, email FROM users ORDER BY created_at DESC LIMIT $1 OFFSET $2",
"params": [20, 0]
}
Increment the offset by the limit for each page: 0, 20, 40, 60...
Join Queries
{
"sql": "SELECT u.name, o.total, o.status FROM users u JOIN orders o ON u.id = o.user_id WHERE o.status = $1 ORDER BY o.created_at DESC LIMIT $2",
"params": ["completed", 10]
}
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.
- 2mo ago First seen · 294 lines · 26 tokens per session scan A f1c0559a8d38
postgres is a skill published in the GitHub repository tallclub/matimo (18 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 1,923 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-08-30.
postgres compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| postgrestallclub/matimo | Skill | 18 | yesterday | MIT | A | 26 | Claude Code, Codex |
| alloydb-basicsgoogle/skills | Skill | 22k | yesterday | Apache-2.0 | A | 72 | Claude Code, Codex |
| postgresql-table-designwshobson/agents | Skill | 42k | yesterday | MIT | A | 37 | Claude Code |
| db-repairgarrytan/gbrain | Skill | 32k | today | MIT | A | 96 | Claude Code |
| volcengine-rds-postgresqlbytedance/agentkit-samples | Skill | 484 | today | Apache-2.0 | A | 63 | Claude Code, Codex |
| dsqlawslabs/agent-plugins | Skill | 937 | yesterday | Apache-2.0 | A | 246 | Claude Code |
| analyzing-insights-across-teamsPostHog/posthog-foss | Skill | 728 | yesterday | MIT | A | 115 | Claude Code, Codex |