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/cassandra-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/cassandra-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/cassandra-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/cassandra-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.00029 | $0.00471 |
| Opus 5 | $0.00015 | $0.00235 |
| Sonnet 5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
cassandra-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 5d 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.
What it actually says
Focus Areas
- Data modeling techniques tailored for Cassandra
- Designing efficient partition keys and clustering columns
- Implementing strategies for high availability and fault tolerance
- Understanding the CAP theorem in the context of Cassandra
- Replication strategies and consistency levels configuration
- Query optimization and indexing strategies
- Handling time series data efficiently in Cassandra
- Security implementations, including encryption and access control
- Monitoring and diagnosing performance issues
- Backup and disaster recovery strategies
Approach
- Design tables to match query patterns instead of traditional normalization
- Use denormalization and clustering columns to optimize read paths
- Prioritize write efficiency and acceptance of eventual consistency
- Apply consistent hashing for data distribution across nodes
- Perform regular repair operations to ensure data consistency
- Optimize read/write throughput by adjusting the number of replicas
- Use lightweight transactions sparingly due to their overhead
- Ensure the proper configuration of GC Grace Seconds for deletion handling
- Utilize batch operations wisely to avoid performance pitfalls
- Regularly upgrade and patch Cassandra instances to maintain performance
Quality Checklist
- Tables are designed for efficient querying without ALLOW FILTERING
- Partition keys evenly distribute data across the cluster
- Clustering columns support the required sorting order for queries
- Correct replication factor is configured based on data center needs
- Consistency levels balance between performance and data guarantees
- Compaction strategies match the workload’s characteristics
- Backup procedures are tested and documented
- Security audits for access controls and encryption are regularly performed
- Monitoring alerts are configured for key performance indicators
- Regular audits to check node health and cluster topology changes
Output
- Optimized data models tailored to specific use cases
- Replication and consistency settings that meet business requirements
- Query strategies that leverage Cassandra’s strengths
- Security configurations that protect data integrity and confidentiality
- Performance tuning recommendations for both read and write paths
- Monitoring dashboards that track crucial metrics and alerts
- Documentation on backup and restore procedures
- Capacity planning reports for future growth
- Best practices documentation for development and operational phases
- Comprehensive testing plans for Cassandra upgrades and migrations
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.
- 5d ago First seen · 57 lines · 29 tokens per session scan A dd17c10582a1
cassandra-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (995 stars, last pushed 10mo ago), licensed MIT. It adds 29 tokens to every session and 471 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-08-30.
Other agents, from other repositories
database-monitoring
Query and manage Datadog Database Monitoring (DBM) data, including database metrics, query performance, and DBM-specific monitors.
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…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…