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 Indie-Kit/nextjs-saas-starter --skill db-handlergit clone --depth 1 https://github.com/Indie-Kit/nextjs-saas-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/skills/indie-kit/nextjs-saas-starter/db-handler)<a href="https://agentmods.dev/skills/indie-kit/nextjs-saas-starter/db-handler"><img src="https://agentmods.dev/badge/skills/indie-kit/nextjs-saas-starter/db-handler/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/indie-kit/nextjs-saas-starter/db-handler"><img src="https://agentmods.dev/badge/skills/indie-kit/nextjs-saas-starter/db-handler.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.00017 | $0.00134 |
| Opus 5.5 | $0.00007 | $0.00054 |
| Sonnet 5.5 | $0.00003 | $0.00027 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
db-handler 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 1mo 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
DB Handler
Instructions
- Use
npm run db:generateto generate migrations after schema changes. - Use
npm run db:migrateto apply migrations. - Use
drizzle-ormfor queries (e.g.,eq,and,or). - Schema files are located in
src/db/schema/. - IMPORTANT: All schema files must be exported from
src/db/schema/index.ts. - Connection string is
DATABASE_URL.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 17 lines · 17 tokens per session scan A b661c038453b
db-handler is a skill published in the GitHub repository Indie-Kit/nextjs-saas-starter (28 stars, last pushed 20d ago), licensed MIT. It adds 17 tokens to every session and 134 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.
Other skills, from other repositories
use-miller
Build, configure, provision, diagnose, verify, deploy, or extend an application created from the Miller starter. Use for projects containing miller.config.json, especially when creating an app, setting up production, configuring self-hosted Better Auth or Stripe, integrating either Next.js or an independent browser…
create-miller
Create a new application from the Miller starter and guide its owner through naming, local setup, provider credentials, verification, and optional production setup. Use when a user asks to start, scaffold, bootstrap, or create a Miller application before a miller.config.json project exists.
clone-production
Clone a production database with automatic PII anonymization.
migration-start
Begin a zero-downtime schema migration using pgroll.
branch-create
Create an isolated database branch for feature development.
migration-rollback
Undo an in-progress migration that hasn't been completed yet.