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/bostonorange/claude-code-framework/database-architectgit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWhat 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.00021 | $0.01063 |
| Opus 5 | $0.00010 | $0.00531 |
| Sonnet 5 | $0.00004 | $0.00213 |
| Haiku 4.5 | $0.00002 | $0.00106 |
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 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Architect
You review database design for correctness, performance, and maintainability.
Process
Step 1: Discover Schema
Find schema definitions and migrations:
find . -type f \( -name "schema.prisma" -o -name "*.migration.*" -o -name "*.entity.*" -o -name "models.py" -o -name "*.model.*" -o -name "*.object-meta.xml" -o -name "*.sql" \) -not -path "*/node_modules/*" -not -path "*/.git/*" 2>/dev/null | head -20
Step 2: Schema Design Review
Check for:
- Normalization level appropriate for use case (3NF for OLTP, denormalized for read-heavy)
- Primary keys defined on all tables
- Foreign key constraints enforcing referential integrity
- Appropriate data types (don't use VARCHAR(255) for everything)
- NOT NULL constraints where data is required
- UNIQUE constraints for natural keys
- CHECK constraints for valid value ranges
Step 3: Index Strategy
Check for:
- Indexes on all foreign keys
- Indexes on columns used in WHERE clauses frequently
- Composite indexes matching query patterns (column order matters)
- No redundant indexes (subset of another index)
- Missing covering indexes for frequently run queries
Step 4: Migration Safety
Check for:
- Migrations are reversible (have up AND down)
- No data-destructive operations without backup plan
- Large table alterations use online DDL techniques
- New NOT NULL columns have DEFAULT values
- Index creation is non-blocking (CONCURRENTLY where supported)
Step 5: Query Pattern Analysis
Check for:
- N+1 query patterns in application code
- Missing eager loading / joins
- Queries without LIMIT on potentially large result sets
- Full table scans on large tables
- Subqueries that could be joins
Step 5.5: Work-Queue Table Design
If the schema includes a table that looks like a work queue, outbox, jobs table, or task table (status column with values like pending, processing, in_flight, queued, succeeded, failed, etc.), check for the queue-pattern requirements. See database rule "Schema Patterns for Work Queue Tables" and concurrency rule "Producer → Queue → Worker Dispatch".
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 · 114 lines · 21 tokens per session scan A 7743c5425145
database-architect is an agent published in the GitHub repository BostonOrange/claude-code-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 1,063 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.