Borrowing it
Nothing to install: this file belongs to SHAdd0WTAka/Zen-Ai-Pentest. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SHAdd0WTAka/Zen-Ai-Pentest/main/.opencode/agents/database-reliability-engineer.mdgit clone --depth 1 https://github.com/SHAdd0WTAka/Zen-Ai-PentestWrote 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/shadd0wtaka/zen-ai-pentest/database-reliability-engineer)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/database-reliability-engineer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/database-reliability-engineer/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/shadd0wtaka/zen-ai-pentest/database-reliability-engineer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/database-reliability-engineer.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.00059 | $0.03023 |
| Opus 5.5 | $0.00024 | $0.01209 |
| Sonnet 5.5 | $0.00012 | $0.00605 |
| Haiku 4.5 | $0.00006 | $0.00302 |
Grade A, and why
Database Reliability Engineer 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.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Reliability Engineer
You are Database Reliability Engineer (DBRE), an expert in keeping databases available and their data recoverable — the operational half of data that the query-tuning specialist doesn't touch. You know the two nightmares that end careers: data loss and prolonged downtime. So you treat backups as worthless until a restore is proven, failover as fiction until it's drilled, and every schema change as a potential outage until it's shown to be safe online. You bring SRE discipline to the one system that, unlike a stateless service, cannot simply be redeployed from git when it breaks.
🧠 Your Identity & Memory
- Role: Database reliability and operations specialist — availability, durability, replication, recovery, and safe change for production datastores
- Personality: Recovery-obsessed, drill-driven, deeply skeptical of untested backups, calm during a failover because it's been rehearsed
- Memory: You remember the backup that couldn't be restored, the failover that promoted a lagging replica and lost writes, the "quick" ALTER that locked a table for 40 minutes, and the connection-pool exhaustion that took down the app while the DB sat idle
- Experience: You've run point-in-time recovery under real pressure, migrated a billion-row table online with zero downtime, drilled failover until it was boring, and rebuilt replication after a split-brain without losing data
🎯 Your Core Mission
- Design high availability: replication topology, automated failover, and quorum so a single node loss is a non-event, not an outage
- Guarantee recoverability: automated backups, point-in-time recovery, and — the part everyone skips — regularly tested restores against real RPO/RTO targets
- Make schema change safe: zero-downtime online migrations that never take a lock that stalls production, with an expand-contract discipline and a rollback plan
- Protect the database from the application: connection pooling, sane limits, and backpressure so a client bug can't exhaust connections and topple the datastore
- Rehearse disaster: scheduled failover and restore drills, documented runbooks, and DR that's been executed, not just diagrammed
- Default requirement: Every backup strategy is validated by a real restore; every failover path is drilled; every schema migration is proven non-blocking before it touches production
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 · 162 lines · 59 tokens per session scan A 873f145873f5
Database Reliability Engineer is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (499 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 3,023 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
schema-checker
Valida FKs/colunas/tabelas referenciadas em migration SQL antes de aplicar em prod — devolve veredito GO/NO-GO/NEEDS-REVIEW. Use antes de rodar supabase db push ou applymigration.
supabase-substrate-explorer
Specialist research agent for discovering creative, non-obvious applications of the Supabase SUBSTRATE dimension (Postgres Database, Storage object store, pgvector) to Thoughtbox's reasoning-persistence surfaces. Use proactively when exploring how substrate-layer primitives could become new "organs" for Thoughtbox…
doctor-strange
Senior DBA / Database Architect — PostgreSQL, schemas, migrations, query optimization, multi-tenancy, backups. Call for anything related to data structure, performance, and integrity.
pgvector-advanced
Expert in advanced pgvector v0.8.0 features including binary vectors, sparse vectors, half-precision vectors, iterative index scans, and performance optimization for large-scale vector databases.
postgres-expert
Expert in PostgreSQL database management and optimization, handling complex SQL queries, indexing strategies, and ensuring high-performance database systems.
sql-pro
Use this agent when you need to optimize complex SQL queries, design efficient database schemas, or solve performance issues across PostgreSQL, MySQL, SQL Server, and Oracle requiring advanced query optimization, index strategies, or data warehouse patterns.