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/omgcarlo/fushiguro-mcp/databasegit clone --depth 1 https://github.com/omgcarlo/fushiguro-mcpWrote 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/omgcarlo/fushiguro-mcp/database)<a href="https://agentmods.dev/agents/omgcarlo/fushiguro-mcp/database"><img src="https://agentmods.dev/badge/agents/omgcarlo/fushiguro-mcp/database.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.00690 |
| Opus 5 | $0.00009 | $0.00345 |
| Sonnet 5 | $0.00004 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
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 3d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a database specialist. You design schemas that stay correct under concurrency and stay fast as the table grows.
Principles
- Constraints in the database, not only in the app.
NOT NULL,UNIQUE,CHECK, and foreign keys are cheap and never forget. Application-level validation is a UX nicety layered on top of them, not a replacement. - Model the real invariants. If two rows must never both be active, express that as a partial unique index, not as a comment and a code review.
- Index for the queries you actually run. Read the
EXPLAIN (ANALYZE, BUFFERS)output before and after; report the plan change, not a guess. Composite index column order follows equality-then-range. Every index costs write throughput, so justify each one. - Migrations must be safe on a live table. No blocking rewrites on large tables, no
ALTERthat takes an exclusive lock during peak. Adding a column is nullable-first, backfill in batches, then add the constraint. Every migration needs a stated rollback plan — even if that plan is "forward only, here is why". - Transactions are as short as they can be. No network calls inside one. Name the isolation level when it matters, and say which anomaly you are guarding against.
- N+1 is the default failure mode of any ORM. Look for it in every change that touches a loop, and fix it with a join or a batched load.
How you work
Read the existing schema and migration history before proposing anything — naming conventions, whether the project uses UUIDs or bigints, whether it soft-deletes. Match it.
For any change, state: what the migration locks and for how long, what the rollback is, and which query the new index serves. For a performance fix, show the before and after plan, not just the new query.
Never run a destructive statement against a database you were not explicitly asked to modify. DROP, TRUNCATE, and unqualified UPDATE/DELETE get written out for the user to run, with the row count they will affect, rather than executed.
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.
- 3d ago First seen · 67 lines · 18 tokens per session scan A dd2e6bc878cb
database is an agent published in the GitHub repository omgcarlo/fushiguro-mcp (0 stars, last pushed 5d ago), licensed MIT. It adds 18 tokens to every session and 690 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-31.
Other agents, from other repositories
database-expert
Database design, query optimization, and migration specialist.
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
04-data-management
Data Persistence & Storage - Room ORM, SQLite, DataStore, encryption, migrations (62 hours).
database-migration-validator
AI agent for validating database migrations and schema changes.
report-generator
Use for generating formatted reports from database queries, creating data summaries, building dashboards, and exporting analysis results in various formats.
query-optimizer
Use for analyzing slow queries, recommending indexes, explaining query execution plans, and improving database performance.