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/d3mocide/sovereign_watch/database-architectgit clone --depth 1 https://github.com/d3mocide/Sovereign_WatchWrote 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/d3mocide/sovereign_watch/database-architect)<a href="https://agentmods.dev/agents/d3mocide/sovereign_watch/database-architect"><img src="https://agentmods.dev/badge/agents/d3mocide/sovereign_watch/database-architect.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.00067 | $0.00770 |
| Opus 5 | $0.00034 | $0.00385 |
| Sonnet 5 | $0.00013 | $0.00154 |
| Haiku 4.5 | $0.00007 | $0.00077 |
Grade A, and why
database-architect 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 4d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 4d ago First seen · 70 lines · 67 tokens per session scan A 565e2ce714db
database-architect is an agent published in the GitHub repository d3mocide/Sovereign_Watch (92 stars, last pushed 13d ago), licensed AGPL-3.0. It adds 67 tokens to every session and 770 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-30.
Other agents, from other repositories
database-expert
Database design, query optimization, and migration specialist.
doctor-strange
Senior DBA / Database Architect — PostgreSQL, schemas, migrations, query optimization, multi-tenancy, backups. Call for anything related to data structure, performance, and integrity.
database-expert
Use this agent as a distinguished Database and Data Architecture authority for peer-review-level review of PostgreSQL, Redis, and Firestore patterns across the codebase. Covers query optimization, schema design, migration safety, connection pooling, caching strategy, data modeling, consistency patterns, and polyglot…
dba
Octopus 資料庫專家——關聯式 DB 諮詢，專精 SQL Server / SQLite / PostgreSQL 三方言。schema 設計、dialect 差異、migration 影響、索引與效能。只讀 schema/migration 檔，不連實體 DB。.
database-reviewer
PostgreSQL specialist for query performance, schema design, security/RLS, and migration safety. Use PROACTIVELY when writing SQL, creating migrations, designing schemas, or troubleshooting database performance.
database-engineer
Use when creating or modifying database schemas, migrations, or SQL scripts. Follows PostgreSQL conventions: NOT NULL for required fields, plural table naming, and TEXT with CHECK constraints over VARCHAR/CHAR.