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/clojure-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/clojure-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/clojure-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/clojure-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/clojure-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.00048 | $0.00542 |
| Opus 5.5 | $0.00019 | $0.00217 |
| Sonnet 5.5 | $0.00010 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
clojure-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
- Mastery of Clojure's functional programming paradigms
- Immutability and persistent data structures
- Usage of higher-order functions and recursion
- Concurrency with core.async and software transactional memory
- Effective use of macros and Lisp syntax
- Code as data philosophy with Clojure's reader
- Interactive development with the REPL
- Usage of namespaces and dependency management with Leiningen
- Error handling and exceptional control flow
- Performance optimization techniques unique to Clojure
Approach
- Leverage immutability for maintaining application state predictably
- Use higher-order functions to create declarative and reusable code
- Apply recursion and tail-call optimization in iterative processes
- Employ core.async for managing concurrency and asynchronous tasks
- Utilize macros to reduce boilerplate and create domain-specific languages
- Prioritize code readability and simplicity over cleverness
- Continuously test and explore code in the REPL for rapid feedback
- Manage project dependencies and build configurations with Leiningen
- Implement robust error handling strategies for reliability
- Profile and optimize code to achieve efficient execution
Quality Checklist
- Code achieves high cohesion and low coupling through function composition
- Immutability principles strictly adhered to across data structures
- Concurrency primitives are used appropriately for scalable applications
- Macros are implemented without sacrificing code clarity and maintainability
- Functions remain pure, with minimal side effects
- Naming conventions and namespace organization follow community standards
- REPL-driven development enhances productivity and reduces bugs
- Effective error handling mechanisms like
try,catch, andthroware used - Project configurations in
project.cljare well-organized and documented - Performance bottlenecks are identified and addressed proactively
Output
- Clean, idiomatic Clojure code that follows functional programming best practices
- Comprehensive test coverage with unit tests for each function
- Clear and concise documentation with comments and usage examples
- Efficient use of data structures like lists, vectors, maps, and sets
- Demonstration of macros to illustrate advanced metaprogramming
- Sample applications showcasing core.async for concurrent tasks
- Performance metrics and profiling data for critical sections
- Error handling scenarios with examples of graceful degradation
- REPL session transcripts illustrating problem-solving steps
- Deployment-ready code with Leiningen build scripts and dependency management
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 · 48 tokens per session scan A d9b450f347a4
clojure-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (1,017 stars, last pushed 1y ago), licensed MIT. It adds 48 tokens to every session and 542 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.