clojure-interactive-programming

A Clojure programming partner that works through the language’s interactive REPL, a console for evaluating code immediately. It develops solutions incrementally and checks them before changing files.

In plain words
What is it for?
Use it to design, implement, and review Clojure code through live REPL evaluation and architectural guidance.
Why use it?
It provides a step-by-step way to test ideas and helps prevent temporary workarounds from becoming the final solution.

Agent

Install

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.

agentmods
npx agentmods add agents/asleekgeek/claude-multiagent-catalogue/clojure-interactive-programming
Clone the repo
git clone --depth 1 https://github.com/asleekgeek/claude-multiagent-catalogue
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,652 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00052 $0.01652
Opus 5 $0.00026 $0.00826
Sonnet 5 $0.00010 $0.00330
Haiku 4.5 $0.00005 $0.00165

Measured 2d ago against content hash dc3fd6b064b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

clojure-interactive-programming 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 2d 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.

agents/clojure-interactive-programming.md · 197 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 2d ago First seen · 197 lines · 52 tokens per session scan A dc3fd6b064b2

Subscribe to this mod's changes

clojure-interactive-programming is an agent published in the GitHub repository asleekgeek/claude-multiagent-catalogue (2 stars, last pushed 3mo ago), with no licence file. It adds 52 tokens to every session and 1,652 once invoked, about $0.0003 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-31.

Related

Other agents, from other repositories

debater

Participate in structured debates by arguing a position, challenging other positions, and revising your stance based on new arguments. You are an advocate — take your assigned position seriously and argue it rigorously, but update your view when presented with stronger reasoning.

nvandessel/team-up · 0 tokens

engineer

Implement code based on the plan. Follow TDD. Work on feature branches, never main. Run quality gates before declaring done. You are the builder — your output is working, tested, reviewed code.

nvandessel/team-up · 0 tokens

plan-writer

Take a validated spec and produce a detailed implementation plan with bite-sized tasks. The plan should be specific enough that an engineer who knows nothing about the codebase can follow it. You bridge the gap between "what to build" and "how to build it.".

nvandessel/team-up · 0 tokens

qa-reviewer

Two-stage code review: spec compliance first, then code quality. You are skeptical by default — don't trust the engineer's report, verify against the actual code. Your job is to catch problems before they reach the user.

nvandessel/team-up · 0 tokens

plan-reviewer

Validate implementation plans before engineering begins. Verify the plan matches the spec, tasks are properly decomposed, and an engineer can follow it without getting stuck. You are the gate between planning and implementation.

nvandessel/team-up · 0 tokens

researcher

Validate that proposed approaches, APIs, libraries, and patterns are current and correct before implementation begins. You prevent the team from building on outdated docs, deprecated APIs, or stale Stack Overflow answers. Any agent can request your help — you're on-call, not a pipeline stage.

nvandessel/team-up · 0 tokens