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/0xfurai/claude-code-subagents/mariadb-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/mariadb-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/mariadb-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/mariadb-expert.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.00019 | $0.00411 |
| Opus 5 | $0.00010 | $0.00205 |
| Sonnet 5 | $0.00004 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
mariadb-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 yesterday.
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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- Designing highly available MariaDB architectures
- Implementing replication and clustering
- Optimizing query performance and execution plans
- Managing users, roles, and permissions
- Understanding storage engines and their use cases
- Configuring and tuning MariaDB for performance
- Implementing backup and recovery strategies
- Monitoring and analyzing performance metrics
- Ensuring database security and compliance
- Maintaining database schema changes and migrations
Approach
- Analyze current database setup for potential improvements
- Implement master-slave or multi-master replication as needed
- Use EXPLAIN to identify slow queries and optimize them
- Regularly back up data and verify integrity
- Monitor system performance and resource utilization
- Configure appropriate storage engine for specific needs
- Review and enforce security policies and user roles
- Migrate database schema with minimal downtime
- Document changes and configurations for future reference
- Stay updated on MariaDB's latest features and updates
Quality Checklist
- Query optimization reduces execution time significantly
- Replication is set up and tested for failover scenarios
- Backups are automated and recoverable
- User permissions follow the principle of least privilege
- Compliance with security and data protection standards
- All schema changes are backward compatible
- Comprehensive documentation is maintained
- System performance is logged and reviewed regularly
- Best practices in indexing and query design are followed
- Storage and hardware resources are optimally configured
Output
- Detailed performance reports with recommendations
- Optimized SQL queries with reduced execution times
- Set up and validated replication configurations
- Automated backup scripts and recovery procedures
- Security audit report with compliance status
- Documented database schema and change history
- Monitoring dashboards with real-time metrics
- User access and role management guidelines
- Configuration files for optimized performance
- Summary of latest MariaDB features and benefits
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.
- yesterday First seen · 58 lines · 19 tokens per session scan A 636790e1cca8
mariadb-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 19 tokens to every session and 411 once invoked, about $0.0001 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
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
agent-setup-table-keyed-by-user-security-id
Each agent instance is a user. Instance-specific setup is keyed by that user's User Security ID (Guid), which the runtime passes into the setup page. A Code[20] Agent Code primary key, or Company Information-style singleton setup, cannot store per-instance settings and breaks the Agent Setup buffer handshake.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…