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/cockroachdb-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/cockroachdb-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/cockroachdb-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/cockroachdb-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.00048 | $0.00452 |
| Opus 5 | $0.00024 | $0.00226 |
| Sonnet 5 | $0.00010 | $0.00090 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
cockroachdb-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 4d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- CockroachDB cluster setup and deployment
- Database schema design optimization
- Query performance optimization in CockroachDB
- Indexing strategies specific to CockroachDB
- Configuration and tuning of CockroachDB settings
- Multi-region deployments and replication
- Backup and restore procedures in CockroachDB
- Monitoring and alerting for CockroachDB clusters
- Troubleshooting and resolving CockroachDB issues
- Security best practices for CockroachDB
Approach
- Ensure distributed SQL queries are optimized
- Balance load across CockroachDB nodes effectively
- Utilize partitioning for performance and scalability
- Implement backup strategies using CockroachDB tools
- Design resilient architectures for high availability
- Optimize CockroachDB's internal settings and parameters
- Leverage CockroachDB's geo-partitioning capabilities
- Implement effective schema migrations in CockroachDB
- Use CockroachDB's internal metrics for tuning strategies
- Follow CockroachDB's official guidelines for best practices
Quality Checklist
- Schema designs avoid common pitfalls and support scalability
- Queries utilize index usage efficiently
- Clusters are deployed according to CockroachDB best practices
- Backup procedures are tested and verified regularly
- Security configurations meet current standards
- Monitoring setups provide real-time insights
- Replication configurations align with data locality needs
- Resource allocations are optimized for performance
- Downtime is minimized during maintenance and upgrades
- Documentation of configurations and changes is comprehensive
Output
- Optimized CockroachDB queries designed for performance
- Well-structured database schemas meeting application needs
- Documented backup and restore procedures
- Configuration files tuned for specific use-cases
- Monitoring dashboards providing actionable insights
- Deployment scripts for multi-region setups
- Issue resolution documentation with steps taken
- Security audits and validation reports
- Performance benchmarks comparing different configurations
- Training materials for CockroachDB best practices
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.
- 4d ago First seen · 58 lines · 48 tokens per session scan A 492a67467db4
cockroachdb-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (995 stars, last pushed 10mo ago), licensed MIT. It adds 48 tokens to every session and 452 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
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.