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/textura-agency/next16-claude-starterWrote 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/textura-agency/next16-claude-starter/db)<a href="https://agentmods.dev/commands/textura-agency/next16-claude-starter/db"><img src="https://agentmods.dev/badge/commands/textura-agency/next16-claude-starter/db/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/textura-agency/next16-claude-starter/db"><img src="https://agentmods.dev/badge/commands/textura-agency/next16-claude-starter/db.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.00011 | $0.00236 |
| Opus 5 | $0.00005 | $0.00118 |
| Sonnet 5 | $0.00002 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
db 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 11d 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
Supabase task: $ARGUMENTS
Use the supabase-db skill. The things that go wrong first:
- Connection strings are not interchangeable. Runtime → Supavisor transaction
pooler (6543, no prepared statements). Migrations → direct connection (5432).
Store both, zod-validated in
src/env.ts, server-only. - Use the current keys — publishable (
sb_publishable_…) client-side, secret (sb_secret_…) server-only. The secret key bypasses RLS entirely. - RLS on every user-data table, with a named role and an index on any column a policy filters. Payload's own tables are excluded — Payload enforces its own access control.
- Never point local dev at production — a schema push will rewrite it.
If Payload owns the schema, Payload owns migrations; use the Supabase CLI only for what sits outside Payload's tables.
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.
- 11d ago First seen · 22 lines · 11 tokens per session scan A bc6ddc9f6021
db is a command published in the GitHub repository textura-agency/next16-claude-starter (113 stars, last pushed 2d ago), licensed Unlicense. It adds 11 tokens to every session and 236 once invoked, about $0.0001 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.
splunk-observability-database-monitoring-setup
Render and validate Splunk Observability Cloud Database Monitoring collector configuration for PostgreSQL, Microsoft SQL Server, and Oracle Database through the Splunk OTel Collector. Keeps secrets out of chat, argv, and rendered files; DB credentials are referenced through Kubernetes Secrets or local env vars.
pg-indexes
Review unused indexes that are safe to drop (pgbot).
rls-plan
Supabase RLS + access-control audit + remediation plan — no SQL until approved.
refactor-stack
Coordinated architecture refactor — change database, cloud provider, or framework with full SDL consistency.
sparc-supabase-admin
🔐 Supabase Admin - You are the Supabase database, authentication, and storage specialist. You design and implement d...