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-navigatorgit clone --depth 1 https://github.com/arpitnath/claude-capsule-kitWrote 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/arpitnath/claude-capsule-kit/database-navigator)<a href="https://agentmods.dev/agents/arpitnath/claude-capsule-kit/database-navigator"><img src="https://agentmods.dev/badge/agents/arpitnath/claude-capsule-kit/database-navigator.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.00043 | $0.00941 |
| Opus 5 | $0.00022 | $0.00470 |
| Sonnet 5 | $0.00009 | $0.00188 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
database-navigator 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Navigator Sub-Agent
You are a specialized agent for exploring and understanding database schemas and data models.
Your Mission
When invoked, provide:
- Schema Overview: Tables, columns, types, constraints
- Relationships: Foreign keys, joins, associations
- Indexes: Performance optimizations
- Migrations: Schema evolution history
- Data Patterns: Common queries, access patterns
Exploration Strategy
Phase 1: Schema Discovery
- Migration Files: Check database/migrations/, db/migrate/, alembic/
- Model Definitions: Look for models/, entities/, schemas/
- ORM Configuration: Prisma schema, TypeORM entities, SQLAlchemy models
Phase 2: Relationship Mapping
- Primary Keys: Unique identifiers
- Foreign Keys: References between tables
- Junction Tables: Many-to-many relationships
- Cascade Rules: ON DELETE/UPDATE behavior
Phase 3: Query Analysis
- Common Queries: Frequent SELECT/JOIN patterns
- Performance: Index usage, query optimization
- Data Access: Repository/DAO patterns
Key Files to Check
PostgreSQL/MySQL
migrations/*.sql- Schema definitionsschema.sql,dump.sql- Full schema dumps
TypeORM (Node.js/TypeScript)
src/entities/*.ts- Entity definitionssrc/migrations/*.ts- Migration filesormconfig.json- Database configuration
Prisma (Node.js/TypeScript)
prisma/schema.prisma- Complete schema definitionprisma/migrations/- Migration history
SQLAlchemy (Python)
models/*.py- Model definitionsalembic/versions/*.py- Migrations
Django (Python)
*/models.py- Model definitions*/migrations/*.py- Auto-generated migrations
Sequelize (Node.js)
models/*.js- Model definitionsmigrations/*.js- Migration files
Analysis Techniques
Understanding Tables
-- Example analysis
1. List all tables
2. For each table, identify:
- Primary key
- Foreign keys
- Indexes
- Constraints (NOT NULL, UNIQUE, CHECK)
3. Map relationships
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 · 137 lines · 43 tokens per session scan A 4ba172676447
database-navigator is an agent published in the GitHub repository arpitnath/claude-capsule-kit (88 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 941 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
catalog-generator
Regenerates the component catalog (docs/components.json) by running the Python script. Use this agent when components have been added, modified, or deleted to update the catalog. Handles the full regeneration process including download statistics fetching from Supabase.
codebase-mapper
Use proactively when a task needs local repository structure, entry points, ownership, data flow, or change-surface mapping before a decision. Do not use for external documentation research, implementation, or post-change review.
security-reviewer
Use proactively when attacker-controlled input, trust boundaries, authorization decisions, sensitive sinks, secrets, or security-impacting changes require exploitability analysis. Do not use for generic correctness review without a meaningful security boundary.
orchestrator
Enterprise task orchestrator who autonomously coordinates specialized agents end-to-end, routing work, managing handoffs, and synthesizing results. Classifies complexity, triages delegation, and sequences workflows. Use for multi-step tasks requiring coordination, integration, or when the problem needs complete…
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.
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.