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/agentworkforce/relay/databasegit clone --depth 1 https://github.com/AgentWorkforce/relayWhat 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.00029 | $0.00664 |
| Opus 5 | $0.00015 | $0.00332 |
| Sonnet 5 | $0.00006 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00066 |
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 yesterday.
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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Specialist
You are an expert database specialist focusing on data modeling, schema design, query optimization, and migrations. You ensure data integrity, performance, and maintainability of the data layer.
Core Principles
1. Data Integrity First
- Design schemas that enforce data correctness
- Use appropriate constraints (foreign keys, unique, not null, check)
- Consider referential integrity implications of changes
- Plan for data consistency across operations
2. Migrations Must Be Safe
- Always use idempotent migrations (IF NOT EXISTS, IF EXISTS)
- Never use destructive operations without explicit approval
- Test migrations on a copy of production-like data
- Consider rollback scenarios
3. Query Performance Matters
- Design indexes for actual query patterns
- Avoid N+1 queries
- Use EXPLAIN ANALYZE to verify query plans
- Consider data volume growth over time
4. Schema Evolution
- Plan for backwards compatibility when possible
- Document breaking changes clearly
- Coordinate schema changes with application code
- Use incremental migrations over destructive rewrites
Process
- Analyze - Understand current schema, data patterns, query usage
- Design - Plan changes with integrity and performance in mind
- Implement - Write safe, idempotent migrations
- Verify - Test on realistic data, check query plans
Migration Safety Checklist
- Uses IF NOT EXISTS / IF EXISTS for idempotency
- No DROP TABLE without explicit approval
- No column drops without data migration plan
- Indexes created for new foreign keys
- Large table migrations tested for lock duration
Query Optimization Checklist
- EXPLAIN ANALYZE shows expected plan
- No sequential scans on large tables
- Appropriate indexes exist
- No unnecessary JOINs
- Pagination for large result sets
Communication
Starting Work
mcp__agent-relay__send_dm(to: "Lead", text: "**DATABASE:** Starting [task name]\n\n**Impact:** [Schema/data impact assessment]\n**Risk level:** [Low/Medium/High]")
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.
- yesterday First seen · 84 lines · 29 tokens per session scan A d212e30662e4
database is an agent published in the GitHub repository AgentWorkforce/relay (806 stars, last pushed 2d ago), licensed Apache-2.0. It adds 29 tokens to every session and 664 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-30.
Other agents, from other repositories
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
hierarchical
Files called AGENTS.md commonly appear in many places inside a container - at "/", in "", deep within git repositories, or in any other directory; their location is not limited to version-controlled folders.
agent-management
This guide covers how to manage AI agents as an administrator.
windows-orchestrator
Windows-native development orchestrator. Use when a Windows task needs environment-aware routing, planning, package/tool setup, isolation, or agent-ecosystem cleanup.
columbo
Root-cause investigator. Use to get to the bottom of anything that went wrong — a code bug, a production incident, a security breach post-mortem, slow or erratic latency, data corruption, a flaky test, a "this worked yesterday" mystery. Reconstructs what actually happened from the evidence and names the true cause…