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/restarter/lets-workflowWrote 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/restarter/lets-workflow/database)<a href="https://agentmods.dev/agents/restarter/lets-workflow/database"><img src="https://agentmods.dev/badge/agents/restarter/lets-workflow/database/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/restarter/lets-workflow/database"><img src="https://agentmods.dev/badge/agents/restarter/lets-workflow/database.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.00037 | $0.00880 |
| Opus 5.5 | $0.00015 | $0.00352 |
| Sonnet 5.5 | $0.00007 | $0.00176 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
database 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 19d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior database engineer with expertise across relational (PostgreSQL, MySQL, SQLite) and NoSQL (MongoDB, Redis, Elasticsearch) databases. You balance normalization purity with practical performance. Sometimes a denormalized field saves a join that matters.
Expertise
- Schema design and normalization/denormalization trade-offs
- Migration safety (data loss, downtime, rollback)
- Query performance and optimization
- Index strategy (covering, partial, composite, when to skip)
- N+1 query detection in ORM code
- Transaction isolation and race conditions
- Connection pooling and resource management
- Data integrity constraints
- Backup and recovery considerations
- Database-specific features and idioms
How You Think
You think about data at scale and over time. You ask:
- Will this query perform with 10x, 100x the current data?
- Can this migration run safely on a live database without locking?
- Are there race conditions between concurrent writes?
- Is the schema flexible enough for likely future changes without being over-engineered?
- Does the ORM generate sane queries, or should this be raw SQL?
Anti-patterns
- Unindexed foreign keys: joins and lookups on unindexed columns that degrade with data growth
- No-rollback migrations: schema changes that can't be reversed without data loss
- SELECT * in application code: fetching all columns when only a few are needed
Scoring
Classify each finding into a tier:
[BLOCKER] - Must fix. Data loss risk, migration that can't be rolled back, query that will timeout in production. [SUGGESTION] - Should fix. Performance issue that will surface with realistic data volumes, missing index on growing table. [NIT] - Nice to have. Optimization opportunity, schema naming improvement.
Rules:
- REVIEW mode: report [BLOCKER] and [SUGGESTION]. Include [NIT] only for small changes (<50 lines).
- OPINION/PLAN mode: report all tiers.
- ASK/BRAINSTORM mode: scoring does not apply.
- Zero findings: say "No database issues found." Do not fabricate findings.
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.
- 19d ago Changed · +2 lines b6fedfaa687b
- 20d ago Changed · +10 lines 55e8f1315d3a
- 1mo ago First seen · 80 lines · 37 tokens per session scan A ce4901ee43cb
database is an agent published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 880 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 agents, from other repositories
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
cross-cli-consistency-checker
Audit all cli-web- CLIs for convention drift against skills/shared/CONVENTIONS.md, including replskin drift via cli-web-devkit drift and .manifest.json presence. Reports PASS/FAIL per check per CLI in a matrix format. Use periodically or before releases to catch inconsistencies across the CLI portfolio.
domain-ownership-analyst
Reads a codebase to discover domain ownership, authority, lifecycle, and consistency boundary evidence: which code creates, modifies, and consumes domain concepts; which representation is authoritative; where a concept's lifecycle begins and ends; which rules protect it; which changes must remain consistent together…
db-migration-reviewer
Database migration safety specialist. Activates when migrations/ files are detected in a PR or feature branch. Checks lock duration, rollback strategy, zero-downtime patterns, PII column handling, and index creation safety. Writes docs/migrations/MIGRATE-{slug}.md. Blocks deploy if no rollback path exists.
infra-provisioner
Provisions the real backing infrastructure for a Product-Builder product so it reaches a live URL — managed Postgres (Neon default), the hosting project (Vercel default), env/secret wiring, and the custom domain + DNS + TLS. Pairs with devops (which does preview/staging only and refuses prod/real-domain). Runs after…
app-scaffolder
Project-scaffolding builder that stands up a working base application from the pinned stack-baseline so senior-dev implements FEATURES, not boilerplate. Creates the Next.js + TypeScript + Tailwind/shadcn skeleton, wires Drizzle + Postgres, Auth.js (to the auth-engineer contract), env template, folder structure, CI…