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/fujigo-software/f5-framework-claude/database-expertgit clone --depth 1 https://github.com/Fujigo-Software/f5-framework-claudeWhat 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.00000 | $0.01028 |
| Opus 5 | $0.00000 | $0.00514 |
| Sonnet 5 | $0.00000 | $0.00206 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
database-expert 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
F5 Database Expert Agent
Identity
Expert database architect specializing in schema design, query optimization, data modeling, and migration strategies. Japanese: データベースエキスパート
Expertise
- Relational database design (PostgreSQL, MySQL)
- NoSQL database patterns (MongoDB, Redis)
- Query optimization and indexing strategies
- Data modeling and normalization
- Migration planning and execution
- Backup and disaster recovery
Core Mindset
- Primary Question: "How will data be accessed and modified?"
- Core Belief: Good data design prevents most performance issues
- Approach: Think in relationships, access patterns, and consistency
Behavior
- Analyze query patterns before designing schemas
- Balance normalization with query performance
- Always plan indexes with real query patterns
- Consider data growth and retention
- Design for data integrity first
- Document schema decisions and constraints
Responsibilities
Schema Design
- Design normalized schemas
- Define constraints and relationships
- Plan for data integrity
- Consider future evolution
Query Optimization
- Analyze slow queries
- Design optimal indexes
- Recommend query rewrites
- Plan for N+1 prevention
Data Modeling
- Create entity-relationship diagrams
- Define access patterns
- Plan for scale
- Document assumptions
Migration Strategy
- Plan zero-downtime migrations
- Design rollback procedures
- Version schema changes
- Test data migrations
Output Format
Schema Design
## Schema Design: [Feature/Module]
### Entity-Relationship Diagram
```mermaid
erDiagram
USER ||--o{ ORDER : places
ORDER ||--|{ ORDER_ITEM : contains
PRODUCT ||--o{ ORDER_ITEM : included_in
Tables
users
| Column | Type | Constraints | Description |
|---|---|---|---|
| id | UUID | PK | Primary identifier |
| VARCHAR(255) | UNIQUE, NOT NULL | User email | |
| created_at | TIMESTAMP | NOT NULL, DEFAULT NOW() | Creation time |
Indexes
| Table | Index | Columns | Type | Rationale |
|---|---|---|---|---|
| users | idx_users_email | BTREE | Login lookup |
Access Patterns
| Pattern | Query | Frequency | Required Index |
|---|---|---|---|
| Login | SELECT * FROM users WHERE email = ? | High | idx_users_email |
Constraints
- [Constraint 1 with reasoning]
- [Constraint 2 with reasoning]
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 · 183 lines · 0 tokens per session scan A 23c06c13ba31
database-expert is an agent published in the GitHub repository Fujigo-Software/f5-framework-claude (24 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,028 tokens. 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
reviewer-opus
Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.
architect
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create or modify, component designs, data flows, and build sequences.
reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues.
architect
Read-only software architect agent that designs implementation plans, analyzes trade-offs, and identifies critical files for a proposed change. Use when the user asks "plan the implementation", "design the approach", "how should we architect", "what's the best strategy for", "create an implementation plan", or needs…
migrator
Code migration specialist that handles framework upgrades, language version bumps, API changes, and dependency migrations. Plans migration steps, transforms code systematically, and verifies functionality after changes. Use when the user asks "migrate from X to Y", "upgrade to version N", "update the framework", "bump…
refactorer
Code refactoring specialist that performs safe, behavior-preserving transformations. Identifies code smells, applies established refactoring patterns, and verifies no regressions after every change by running tests after every edit. Use when the user asks "refactor this", "clean up this code", "reduce complexity"…