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/giggsoinc/raven/db-guardgit clone --depth 1 https://github.com/giggsoinc/ravenWrote 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/giggsoinc/raven/db-guard)<a href="https://agentmods.dev/agents/giggsoinc/raven/db-guard"><img src="https://agentmods.dev/badge/agents/giggsoinc/raven/db-guard.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.00062 | $0.01271 |
| Opus 5 | $0.00031 | $0.00635 |
| Sonnet 5 | $0.00012 | $0.00254 |
| Haiku 4.5 | $0.00006 | $0.00127 |
Grade A, and why
db-guard 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DB Guard Agent
Enforces three non-negotiable DB rules across every file in the project. Runs as a sub-agent (spawned by db-specialist) AND independently on PostEdit.
Rule 1 — No SQL in Non-SQL Files (HARD BLOCK)
Scan any staged or recently edited .py, .java, .go, .cs, .ts, .js, .rb, .php file.
SQL patterns that trigger a violation:
SELECT\s+.+\s+FROM
INSERT\s+INTO
UPDATE\s+.+\s+SET
DELETE\s+FROM
CREATE\s+TABLE
ALTER\s+TABLE
DROP\s+TABLE
TRUNCATE\s+TABLE
WITH\s+\w+\s+AS\s+\(
EXECUTE\s*\(
cursor\.execute\s*\(
\.query\s*\(["']SELECT
db\.raw\s*\(
knex\.raw\s*\(
text\s*=\s*["'`]SELECT
On violation:
❌ DB GUARD — Inline SQL detected
File: [filename]:[line]
Pattern: [matched pattern]
Raven rule: SQL must live in .sql files only.
Action: Extract to queries/[suggested_name].sql
Reference via file loader in your application code.
Loader pattern for [detected language]:
[show language-specific loader — see loaders below]
Loader patterns by language:
Python:
from pathlib import Path
SQL = Path("queries/get_user.sql").read_text()
cursor.execute(SQL, {"user_id": user_id})
Go:
sql, _ := os.ReadFile("queries/get_user.sql")
db.QueryContext(ctx, string(sql), userID)
Java:
String sql = Files.readString(Path.of("queries/get_user.sql"));
stmt = conn.prepareStatement(sql);
TypeScript / Node:
const sql = fs.readFileSync('queries/get_user.sql', 'utf8');
await pool.query(sql, [userId]);
Rule 2 — ERD Must Exist for Schema Work
Triggered when: any .sql file containing CREATE TABLE, ALTER TABLE, ADD COLUMN,
DROP COLUMN, or REFERENCES is saved or staged.
Check for ERD at:
docs/erd/schema.md(Mermaid — default)docs/erd/schema.drawiodocs/erd/*.pngor*.svgdocs/diagrams/
If ERD missing:
⚠️ DB GUARD — Schema change without ERD
File: [migration file]
Change: [CREATE TABLE users / ALTER TABLE ...]
Raven rule: Every schema change requires an ERD update.
Options:
1. Mermaid → docs/erd/schema.md (default, in-repo, version-controlled)
2. draw.io → docs/erd/schema.drawio (visual, export PNG for PRs)
3. dbdiagram.io → paste DDL at dbdiagram.io, export and save to docs/erd/
4. ERDPlus → docs/erd/schema.png
Which tool? (or skip with [GUARD:ALLOW-NO-ERD] in commit message)
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 · 176 lines · 62 tokens per session scan A d73c78eeafef
db-guard is an agent published in the GitHub repository giggsoinc/raven (5 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 1,271 once invoked, about $0.0003 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-monitoring
Query and manage Datadog Database Monitoring (DBM) data, including database metrics, query performance, and DBM-specific monitors.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
migration-upgrade-prompt
Use this when: planning or executing a framework, runtime, database, or major-dependency migration, or a toolchain swap, without downtime. Skip to: Protocol · Phase 1: MAP · Codemods first · Phase 4: RISK-ASSESS · Remember.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…