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.
git clone --depth 1 https://github.com/jezweb/claude-skillsWrote 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/commands/jezweb/claude-skills/db-seed)<a href="https://agentmods.dev/commands/jezweb/claude-skills/db-seed"><img src="https://agentmods.dev/badge/commands/jezweb/claude-skills/db-seed/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/commands/jezweb/claude-skills/db-seed"><img src="https://agentmods.dev/badge/commands/jezweb/claude-skills/db-seed.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.00007 | $0.00118 |
| Opus 5 | $0.00003 | $0.00059 |
| Sonnet 5 | $0.00001 | $0.00024 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
db-seed 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 9d 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
Load the db-seed skill.
Parse $ARGUMENTS for:
- Volume:
small(5-10 rows),medium(20-50),large(100+). Default: small - Purpose:
dev,demo, ortest. Default: dev
Examples: /db-seed large demo, /db-seed, /db-seed test
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.
- 9d ago First seen · 13 lines · 7 tokens per session scan A d89dbd214b4a
db-seed is a command published in the GitHub repository jezweb/claude-skills (999 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 118 once invoked, about $0.0000 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-30.
Other commands, from other repositories
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
migrate
Generate and manage database migrations.
pr
Create a pull request using the git-pushing skill.
db-migrate.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.