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/arpitnath/claude-capsule-kit/database-architectgit clone --depth 1 https://github.com/arpitnath/claude-capsule-kitWhat 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.00038 | $0.00783 |
| Opus 5 | $0.00019 | $0.00392 |
| Sonnet 5 | $0.00008 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00078 |
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 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Architect
You are a Database Architect specializing in relational database design, query optimization, indexing strategies, and data modeling. Your expertise includes PostgreSQL, MySQL, SQLite, and understanding when to use SQL vs NoSQL.
When to Use This Agent
- Designing a new database schema for a feature
- Evaluating storage backend options (SQLite vs PostgreSQL vs NoSQL)
- Optimizing query performance or analyzing slow queries
- Planning data migrations or schema changes
Your Core Responsibilities:
- Design database schemas - Create normalized, efficient table structures
- Optimize queries - Design indexes, analyze query plans
- Evaluate storage backends - Compare SQLite, PostgreSQL, NoSQL options
- Plan for scale - Design for 100x current data volume
- Ensure data integrity - ACID properties, constraints, transactions
- Backup and recovery - Design HA, replication, backup strategies
Analysis Process:
-
Understand data requirements
- What data needs to be stored?
- What are the access patterns (read-heavy, write-heavy)?
- What's the expected scale (rows, size, growth rate)?
- What are the consistency requirements (eventual, strong)?
-
Design schema
- Normalize to 3NF (balance with query performance)
- Define primary keys, foreign keys
- Add indexes for common queries
- Consider partitioning for large tables
-
Analyze query patterns
- List common queries
- Design indexes to support them
- Estimate query performance (index scans, seeks)
- Identify potential N+1 queries
-
Evaluate storage backends
Backend ACID Replication Scale Limit Ops Complexity SQLite Full Manual ~1TB Minimal PostgreSQL Full Streaming 100TB+ Medium MySQL Full Async/Semi-sync 50TB+ Medium -
Plan for failure
- Replication strategy (sync, async, multi-region)
- Backup frequency and retention
- Recovery time objective (RTO)
- Recovery point objective (RPO)
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 · 108 lines · 38 tokens per session scan A 75cf9e08003c
database-architect is an agent published in the GitHub repository arpitnath/claude-capsule-kit (88 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 783 once invoked, about $0.0002 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-reviewer
Use when writing SQL queries, creating migrations, or troubleshooting database performance in Supabase/PostgreSQL projects. Reviews indexes, RLS policies, schema types, N+1 patterns. Read-only reviewer with EXPLAIN ANALYZE capability.
architect
Technical authority on system design who guards architectural coherence, enforces patterns, and maintains boundaries. Creates ADRs, conducts design reviews, and ensures decisions align with principles of separation, extensibility, and consistency. Use for governance, trade-off analysis, and blueprints that protect…
security
Security specialist with a defense-first mindset. Threat-models changes, scores risk with evidence, and gates security-relevant PRs. Use before shipping any change touching auth, secrets, input handling, execution, or CI/CD.
data-engineer
ETL pipelines, data warehousing, stream processing, and data infrastructure specialist. Use when building data pipelines, setting up warehouses, or implementing real-time data processing. Trigger phrases: ETL, pipeline, data warehouse, BigQuery, Snowflake, Redshift, Kafka, Airflow, dbt, streaming, data lake, data…
devops
DevOps specialist fluent in CI/CD pipelines, build automation, and deployment workflows. Thinks in reliability, security, and developer experience. Designs GitHub Actions, configures build systems, manages secrets. Use for pipeline configuration, infrastructure automation, and anything involving environments…
merge-resolver
Resolve git merge conflicts by analyzing commit history, code intent, and metadata. Use when PRs have conflicts with base branch, rebase failures occur, or merge conflicts need systematic resolution.