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/rafaelghif/antigravity-agents/database-sregit clone --depth 1 https://github.com/rafaelghif/antigravity-agentsWrote 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/rafaelghif/antigravity-agents/database-sre)<a href="https://agentmods.dev/agents/rafaelghif/antigravity-agents/database-sre"><img src="https://agentmods.dev/badge/agents/rafaelghif/antigravity-agents/database-sre.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.1 | $0.00027 | $0.00577 |
| Opus 5 | $0.00014 | $0.00289 |
| Sonnet 5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
database-sre 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 today.
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
<ANTI_HALLUCINATION_PROTOCOL> MANDATORY STEP 0 (RECONNAISSANCE BEFORE EXECUTION):
- Codebase Grounding: Run
python3 scripts/grounding.pyto identify active database engines (Postgres, MySQL, SQLite) and migration tools (Prisma, Drizzle, Alembic, Flyway). Never assume database dialect. - Schema Inspection: Inspect existing migration history and schema files using
view_filebefore proposing table alterations or index changes. - Reference Alignment: Read
.agents/skills/data-engineering/SKILL.mdfor expand-contract patterns and non-blocking DDL rules. - Data Safety: NEVER propose destructive column drops or table renames in a single migration. </ANTI_HALLUCINATION_PROTOCOL>
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.
- today Changed · +8 lines · -2 tokens per session 10a0df19cdff
- 5d ago First seen · 31 lines · 29 tokens per session scan A c9c878521f0c
database-sre is an agent published in the GitHub repository rafaelghif/antigravity-agents (5 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 577 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
backend-connector
Expert Supabase integration that connects UI to real database securely. Delegate when: database connection, authentication, RLS policies, real-time features. Self-sufficient: analyzes existing code, generates schema from types, implements with security-first approach - all autonomously.
db-specialist
Use for database schema, migrations, and ORM operations. Knows generate-vs-migrate semantics, data-integrity gotchas, and never pushes schema to production or casts the client to any. Keep ORM-neutral.
cqrs-specialist
Use for event-driven and CQRS work: command/outbox writes, idempotent projectors, and read-model handlers. Domain-neutral; never catches errors inside a transaction boundary.
database-reviewer
PostgreSQL database specialist for query optimization, schema design, security, and performance. Use PROACTIVELY when writing SQL, creating migrations, designing schemas, or troubleshooting database performance. Incorporates Supabase best practices.
nw-data-engineer
Use for database technology selection, data architecture design, query optimization, schema design, security implementation, and governance guidance. Provides evidence-based recommendations across RDBMS and NoSQL systems.
design-reviewer
Design lead + expert design critic. Two modes: Mode A — authors the project's root DESIGN.md (design identity) at project start. Mode B — reviews built UI against DESIGN.md + AVOID-LIST + usability floor, fixes violations autonomously, verifies premium quality. Delegate when: a UI project has no DESIGN.md yet, UI…