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/elixir-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/elixir-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/elixir-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/elixir-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/elixir-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.00041 | $0.00417 |
| Opus 5.5 | $0.00016 | $0.00167 |
| Sonnet 5.5 | $0.00008 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
elixir-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
- Functional programming principles in Elixir
- Concurrency with lightweight processes
- Building scalable systems with OTP
- Robust error handling and fault tolerance
- Pattern matching and guard clauses
- Writing maintainable Elixir code
- Understanding of immutability benefits
- Use of the Phoenix framework for web development
- Efficient use of Elixir's macro system
- Developing distributed systems with Elixir
Approach
- Leverage pattern matching for cleaner code
- Implement supervision trees for fault tolerance
- Use processes and GenServers for concurrent tasks
- Utilize immutability for predictable data flows
- Follow best practices for code readability
- Keep functions pure and side-effect free where possible
- Use mix for project management and task automation
- Employ Phoenix for handling real-time communication
- Prioritize performance through benchmarking tools
- Embrace community conventions from style guides
Quality Checklist
- Code follows Elixir style guide conventions
- Functions are small, pure, and focused
- Modules are appropriately named and cohesive
- Test coverage meets or exceeds 90%
- Comprehensive use of documentation with @doc
- Functions thoroughly tested with ExUnit
- No Dialyzer warnings remain unresolved
- Use of struct types over bare maps
- Refactored code for clarity and simplicity
- Performance is regularly profiled and optimized
Output
- Idiomatic Elixir code implementing best practices
- Well-structured applications using OTP principles
- Responsive web applications built with Phoenix
- Reliable systems through effective concurrency patterns
- Comprehensive test suites for robust codebases
- Clear documentation and comments throughout code
- Clean module and function organization
- Efficient state management through GenServers
- Clear and descriptive commit messages
- Modular and reusable code components
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 · 58 lines · 41 tokens per session scan A 69e21a2e980f
elixir-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (1,017 stars, last pushed 1y ago), licensed MIT. It adds 41 tokens to every session and 417 once invoked, about $0.0002 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
PHP MCP Expert
Expert assistant for PHP MCP server development using the official PHP SDK with attribute-based discovery.
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
ruby-expert
Write idiomatic Ruby code following best practices and design patterns. Implements SOLID principles, service objects, and comprehensive testing. Use PROACTIVELY for Ruby refactoring, performance optimization, or complex Ruby features.
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.