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 agentmods add agents/restarter/lets-workflow/databasegit clone --depth 1 https://github.com/restarter/lets-workflowWhat 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 | $0.00037 | $0.00699 |
| Opus 5 | $0.00018 | $0.00349 |
| Sonnet 5 | $0.00007 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
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 2d 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 — 80 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.
- 2d 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 9d ago), licensed MIT. It adds 37 tokens to every session and 699 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.