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/clojure-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWhat 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.00048 | $0.00542 |
| Opus 5 | $0.00024 | $0.00271 |
| Sonnet 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 yesterday.
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.
- yesterday 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 (992 stars, last pushed 10mo ago), licensed MIT. It adds 48 tokens to every session and 542 once invoked, about $0.0002 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.