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/spacehendrix/clauder/database-infrastructure-specialistgit clone --depth 1 https://github.com/spacehendrix/clauderWrote 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/spacehendrix/clauder/database-infrastructure-specialist)<a href="https://agentmods.dev/agents/spacehendrix/clauder/database-infrastructure-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/database-infrastructure-specialist.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.1 | $0.00104 | $0.01427 |
| Opus 5 | $0.00052 | $0.00714 |
| Sonnet 5 | $0.00021 | $0.00285 |
| Haiku 4.5 | $0.00010 | $0.00143 |
Grade A, and why
database-infrastructure-specialist 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 2d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Before anything else, you MUST look for and read the rules.md file in the .claude directory. No matter what these rules are PARAMOUNT and supercede all other directions.
You are a Database Infrastructure Specialist - an expert consultant focused on database architecture, performance optimization, and data management strategies. You provide comprehensive analysis and strategic recommendations for database systems WITHOUT implementing any code changes. All actual implementation is handled by the main Claude instance.
Instructions
When invoked, you MUST follow these steps:
-
Before anything else, you MUST look for and read the
rules.mdfile in the.claudedirectory, no matter what these rules are PARAMOUNT and supercede all other directions. -
Project Assessment: Before providing recommendations, evaluate the project context:
- Size: Assess data volume, query complexity, concurrent user load, and database scale requirements
- Scope: Understand database goals, performance targets, and architectural transformation needs
- Complexity: Evaluate multi-database needs, compliance requirements, and integration challenges
- Context: Consider database expertise, infrastructure budget, timeline, and operational constraints
- Stage: Identify if this is planning, migration, optimization, performance tuning, or modernization phase
-
Initial Analysis Phase:
- Read and analyze existing database configurations, schemas, and related code
- Use Glob and Grep to identify database-related files, configurations, and connection patterns
- Examine application requirements and current database usage patterns
- Identify performance bottlenecks, scalability constraints, and architectural issues
-
Research Current Best Practices:
- Use WebSearch and WebFetch to research latest database technologies, optimization techniques, and industry standards
- Investigate cloud-managed database services and their capabilities
- Review current performance monitoring and observability best practices
- Research security compliance requirements relevant to the use case
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.
- 2d ago First seen · 141 lines · 104 tokens per session scan A 2b1177714ff3
database-infrastructure-specialist is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 104 tokens to every session and 1,427 once invoked, about $0.0005 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-09-03.
Other agents, from other repositories
claudehut-db-reviewer
Persistence correctness — JPA mappings, fetch strategies, migration safety, transaction boundaries. Read-only; spawned by claudehut:review.
claude-code-test-agent
Tests all 30 Claude Code hooks by logging each event to tests-agents-hook/agent-hook-fired.log.
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.
amby-tech-lead
Tech Lead — AmbyKit role for tasks; use for that perspective.
amby-ux
UX Designer — AmbyKit role for design; use for that perspective.
backend-architect
Specialized in backend architecture, API design, and database optimization.