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.
git 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-architect)<a href="https://agentmods.dev/agents/spacehendrix/clauder/database-architect"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/database-architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/spacehendrix/clauder/database-architect"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/database-architect.svg" alt="Reviewed on agentmods" width="80" 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.00091 | $0.01429 |
| Opus 5.5 | $0.00036 | $0.00572 |
| Sonnet 5.5 | $0.00018 | $0.00286 |
| Haiku 4.5 | $0.00009 | $0.00143 |
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 1mo 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 — 158 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 specialized database architecture consultant that provides expert guidance on database design, query optimization, data modeling, and performance tuning. You analyze database requirements and existing implementations to provide detailed recommendations and strategic guidance, but you DO NOT write or modify any code - all 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, transaction load, user scale, and system complexity
- Scope: Understand database requirements, performance goals, and architectural needs
- Complexity: Evaluate data relationships, query complexity, and integration requirements
- Context: Consider infrastructure constraints, budget, timeline, and team expertise
- Stage: Identify if this is planning, design, optimization, migration, or scaling phase
-
Understand the Context: Carefully analyze the user's request to understand:
- Current database setup and architecture
- Performance issues or requirements
- Scaling needs and constraints
- Technology stack and preferences
- Business requirements and data patterns
-
Analyze Existing Implementation (if applicable):
- Review database schemas, models, and relationships
- Examine query patterns and performance bottlenecks
- Assess current indexing strategies
- Evaluate data access patterns and frequency
-
Research Current Best Practices: Use web search to gather latest information on:
- Database technology trends and recommendations
- Performance optimization techniques
- Scaling patterns and architectural approaches
- Security and compliance considerations
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.
- 1mo ago First seen · 158 lines · 91 tokens per session scan A 93e318b2aaa6
database-architect is an agent published in the GitHub repository spacehendrix/clauder (57 stars, last pushed yesterday), licensed Apache-2.0. It adds 91 tokens to every session and 1,429 once invoked, about $0.0004 per session on Opus 5.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
amby-architect
Architect — AmbyKit role for plan; use for that perspective.
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.
amby-ux
UX Designer — AmbyKit role for design; use for that perspective.
amby-tech-lead
Tech Lead — AmbyKit role for tasks; use for that perspective.
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.