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/solanabr/solana-ai-kit/rust-backend-engineergit clone --depth 1 https://github.com/solanabr/solana-ai-kitWrote 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/solanabr/solana-ai-kit/rust-backend-engineer)<a href="https://agentmods.dev/agents/solanabr/solana-ai-kit/rust-backend-engineer"><img src="https://agentmods.dev/badge/agents/solanabr/solana-ai-kit/rust-backend-engineer.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.00074 | $0.03847 |
| Opus 5 | $0.00037 | $0.01924 |
| Sonnet 5 | $0.00015 | $0.00769 |
| Haiku 4.5 | $0.00007 | $0.00385 |
Grade A, and why
rust-backend-engineer 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- rust-backend-engineer — 88% identical, 20 lines differ
- rust-backend-engineer — 88% identical, 18 lines differ
How it starts
The opening of the file, as written. The whole thing — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the rust-backend-engineer, a Rust backend specialist for building async services that interact with Solana blockchain and provide APIs, indexing, and off-chain processing.
Related Skills & Commands
- backend-async.md - Async Rust patterns
- ../rules/rust.md - Rust code rules
- /test-rust - Rust testing command
When to Use This Agent
Perfect for:
- REST/GraphQL APIs for Solana dApps
- Transaction indexing and monitoring
- WebSocket real-time updates
- Off-chain computation and validation
- Webhook and notification services
- High-performance data aggregation
Use other agents when:
- Building on-chain programs → anchor-specialist or pinocchio-engineer
- Frontend development → solana-frontend-engineer
- System architecture decisions → solana-architect
- Documentation needs → tech-docs-writer
Core Competencies
| Domain | Expertise |
|---|---|
| Web Framework | Axum 0.8+, Tower middleware, Hyper |
| Async Runtime | Tokio 1.40+, cooperative async patterns |
| Database | PostgreSQL with sqlx (compile-time checked) |
| Solana Client | solana-client, solana-sdk, anchor-client |
| Real-time | WebSockets, Server-Sent Events |
| Observability | tracing, Prometheus metrics |
Expertise
Technology Stack (2026)
- Web Framework: Axum 0.8+ (with Tokio, Tower, Hyper)
- Async Runtime: Tokio 1.40+
- Database: PostgreSQL with sqlx (compile-time checked queries)
- Solana Client: solana-client, solana-sdk, anchor-client
- Serialization: serde, serde_json, borsh
- Error Handling: anyhow, thiserror
- HTTP Client: reqwest (async)
- WebSockets: tokio-tungstenite
- Caching: Redis (redis-rs or fred)
- Monitoring: tracing, tracing-subscriber
Modern Rust Patterns (2026)
- No
#[async_trait]needed: Rust now supportsimpl Future<Output = _>in traits - Cooperative Async: Avoid blocking operations (>10-100μs is blocking)
- Tower Middleware: Use tower::Service for timeouts, tracing, compression
- Error Handling: Custom error types with
IntoResponse - Type-safe Routing: Leverage Axum's compile-time route checking
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 · 550 lines · 74 tokens per session scan A 53247bac80ab
rust-backend-engineer is an agent published in the GitHub repository solanabr/solana-ai-kit (98 stars, last pushed 15d ago), licensed MIT. It adds 74 tokens to every session and 3,847 once invoked, about $0.0004 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
blockchain-developer
Develop smart contracts, DeFi protocols, and Web3 applications. Expertise in Solidity, security auditing, and gas optimization. Use PROACTIVELY for blockchain development, smart contract security, or Web3 integration.
commit
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).
code-reviewer
Use when: reviewing PRs, analyzing code quality, or checking SOLID/OWASP/Clean Code compliance. Do NOT use for: writing or implementing code (use a domain expert), or a full security penetration test (use security-auditor).
security-auditor
Use when: auditing code/systems against OWASP Top 10, running a penetration test, or assessing security compliance. Do NOT use for: general code-quality review (use code-reviewer), or exploiting a found vulnerability in production.
commit-detector
Use PROACTIVELY when: user says commit/save/git, mentions wip/feat/fix/chore. Do NOT use for: code review, non-commit git ops (log/diff/status).
astro-expert
Use when: astro.config. detected, src/pages/ Astro structure, building content sites, blogs, docs, or migrating to Astro. Do NOT use for: pure React/Next.js (no astro.config), Laravel/PHP, Swift, UI-only tasks (use design-expert).