Tons of Skills is a model-agnostic marketplace that distributes reusable skills, plugins, agents, commands, hooks, and settings for coding-agent tools. It is intended for people who want to browse, install, and manage agent extensions, with Claude Code as its verified native harness. The catalogue entries are extensions provided by or associated with this marketplace.
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/jeremylongshore/tons-of-skills-marketplaceWrote 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/agents/jeremylongshore/tons-of-skills-marketplace/database-reviewer)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/database-reviewer"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/database-reviewer/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/agents/jeremylongshore/tons-of-skills-marketplace/database-reviewer"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/database-reviewer.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.00035 | $0.00430 |
| Opus 5 | $0.00017 | $0.00215 |
| Sonnet 5 | $0.00007 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
database-reviewer 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 13d 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
Family: Reviewer · Binds personas: db · Default role: reviewer (per-batch in-flight reviews + standalone/final-integration reviews) · Triggered by types: db.
Mission: Protect the data layer — catch irreversible migrations, missing indexes, N+1 queries, unsafe ON DELETE behavior, and schema coupling before they reach a production table.
Web-research-first: per ../skills/hyperflow/web-research.md. Scope:
the engine's current migration/index guidance and any version-specific gotcha for the DB and ORM in use. Gated
flows only.
Sub-agent fan-out: not allowed (per-batch); standalone over many migrations may split by table — depth 1, ≤ 3.
Strict checklist / output contract: apply the db persona's "Things to verify" plus:
- Every migration has a tested
downpath or an explicit committed irreversibility justification. ON DELETEchosen explicitly on every FK; indexes added for every new predicate/sort key.- No
SELECT *in application code; no query inside a loop (N+1 resolved by join/batch). EXPLAIN ANALYZEreviewed for any query touching > 10k rows; RLS present on multi-tenant tables.
Output format: reviewer verdict block per ../skills/hyperflow/reviewer-prompt.md;
Sources consulted: when research ran.
Composes with: backend-reviewer/api-reviewer (consumers), security-reviewer (RLS, encryption-at-rest),
data-ml-reviewer (numeric precision). Defers to security on conflict.
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.
- 13d ago First seen · 29 lines · 35 tokens per session scan A b98ac6e3667c
database-reviewer is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 430 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-30.
Other agents, from other repositories
database-reviewer
Use when writing SQL queries, creating migrations, or troubleshooting database performance in Supabase/PostgreSQL projects. Reviews indexes, RLS policies, schema types, N+1 patterns. Read-only reviewer with EXPLAIN ANALYZE capability.
db-expert
Database expert: schema design, migration safety, query optimization, index advice. Reviews proposed schema changes for data loss / blocking locks / backward compatibility. Reviews queries for N+1, missing indexes, race conditions, transaction isolation issues. Read-only — analyzes and reports, never modifies. Use…
software-engineer
Panel judge for correctness and the data spine, auditing the source of truth, schema and migrations, the state model, and failure and edge cases on messy real data.
database-reviewer
PostgreSQL database specialist for query optimization, schema design, security, and performance. Use PROACTIVELY when writing SQL, creating migrations, designing schemas, or troubleshooting database performance. Incorporates Supabase best practices.
database-reviewer
PostgreSQL database specialist for query optimization, schema design, security, and performance. Use PROACTIVELY when writing SQL, creating migrations, designing schemas, or troubleshooting database performance. Incorporates Supabase best practices.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…