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.
git 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/actix-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/actix-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/actix-expert/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/actix-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/actix-expert.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00017 | $0.00426 |
| Opus 5.5 | $0.00007 | $0.00170 |
| Sonnet 5.5 | $0.00003 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
actix-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 1mo 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
- Understanding the Actix actor model
- Mastering Actix Web for HTTP server applications
- Implementing asynchronous programming with Actix
- Employing middleware for cross-cutting concerns
- Managing application state in Actix
- Routing and request handling in Actix
- Error handling and response management
- Utilizing Actix's built-in components effectively
- Debugging and profiling Actix applications
- Performance optimization strategies specific to Actix
Approach
- Follow Rust's ownership and borrowing rules for memory safety
- Leverage async/await for non-blocking IO operations
- Use Actix middleware for logging and authentication
- Prefer strongly-typed state management
- Structure code for clarity and maintainability
- Incorporate best practices for Actix routing
- Handle errors using Result and Actix error handling patterns
- Optimize for concurrency using Actix's actor model
- Use Actix's extractors for request parsing
- Ensure Actix applications can scale gracefully
Quality Checklist
- Use cargo fmt for consistent code formatting
- Adhere to Actix community guidelines and idioms
- Ensure all routes are correctly defined and reachable
- Test middleware and routes for expected behavior
- Validate inputs and handle edge cases appropriately
- Document public APIs using Rustdoc
- Monitor application performance and resource usage
- Ensure zero memory leaks with rigorous testing
- Use Actix's logger for consistent logging output
- Write unit and integration tests for end-to-end coverage
Output
- High-performance Actix web applications
- Well-structured and maintainable Rust code
- Comprehensive test suite for Actix components
- Thorough error handling and logging
- Scalable architecture designed for Actix's concurrency model
- Detailed documentation and tutorials
- Efficient middleware implementations
- Secure applications with input validation
- Clarity in API endpoints and request handling
- Deployment-ready Actix services with minimal dependencies
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.
- 1mo ago First seen · 57 lines · 17 tokens per session scan A bc50a611b9f9
actix-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (1,018 stars, last pushed 1y ago), licensed MIT. It adds 17 tokens to every session and 426 once invoked, about $0.0001 per session on Opus 5.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
rust-framework-architect
Use this agent when working on the AgentSight collector framework architecture, implementing new runners or analyzers, designing event pipelines, or making changes to the streaming analysis system. Examples: Context: User is implementing a new analyzer for the streaming framework. user: 'I need to create a new…
rust-expert
Rust ownership/borrowing, async Rust, Axum/Actix web frameworks, and WASM specialist. Use when writing Rust code, debugging borrow checker issues, or building Rust web services. Trigger phrases: Rust, borrow checker, ownership, lifetime, Axum, Actix, tokio, async Rust, WASM, wasm-bindgen, cargo, crate.
rust-expert
Use when: Cargo.toml present. Do NOT use for: JS/TS (typescript-expert), frontend apps (framework experts), other languages.
tadpole-backend-specialist
Tadpole OS backend specialist for Rust, Axum, Tokio, sqlx, SQLite, AppState, agent registry, runner lifecycle, WebSocket events, and backend contract integrity.
rust-cli-builder
Use this agent when you need to build command-line interface (CLI) applications in Rust, especially when implementing natural language processing tools, shell command generators, or any CLI that requires API integration, user interaction, and command execution. Examples: Context: User wants to create a CLI tool that…
rust-pro
Master Rust 1.75+ with modern async patterns, advanced type system features, and production-ready systems programming. Expert in the latest Rust ecosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming.