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 skills add zcaudate-xyz/foundation-base --skill clojure-replgit clone --depth 1 https://github.com/zcaudate-xyz/foundation-baseWrote 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/skills/zcaudate-xyz/foundation-base/clojure-repl)<a href="https://agentmods.dev/skills/zcaudate-xyz/foundation-base/clojure-repl"><img src="https://agentmods.dev/badge/skills/zcaudate-xyz/foundation-base/clojure-repl/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/skills/zcaudate-xyz/foundation-base/clojure-repl"><img src="https://agentmods.dev/badge/skills/zcaudate-xyz/foundation-base/clojure-repl.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.00823 |
| Opus 5.5 | $0.00021 | $0.00329 |
| Sonnet 5.5 | $0.00011 | $0.00165 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
clojure-repl 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clojure REPL (clojure-mcp-light)
This skill wires Bruce Hauman's clojure-mcp-light toolchain into Kimi Code CLI for this project. It provides delimiter-safe Clojure evaluation and repair via MCP tools.
Available MCP tools
Tool names are prefixed by Kimi as mcp__clojure-light__<tool>:
clojure_eval(code, port?)— evaluate a Clojure form against a running nREPL server.clojure_repair(code)— repair unbalanced delimiters and applycljfmtformatting.list_nrepl_ports()— discover running nREPL servers in the current directory.
Setup (one-time)
The following are already installed for this project:
parinfer-rust(delimiter repair backend)clj-nrepl-eval(nREPL evaluator)clj-paren-repair(delimiter repair + formatting).kimi/mcp-clojure-light/server.py(MCP wrapper, Python venv)~/.kimi/mcp.jsonis registered with theclojure-lightMCP server
Verify the server is reachable:
kimi mcp test clojure-light
If you need to point Kimi at a different config file for testing:
kimi --mcp-config-file /path/to/mcp.json mcp test clojure-light
Core workflow
-
Before evaluating, check for a running REPL:
- Use
list_nrepl_ports. - Or check
.nrepl-portin the project root.
- Use
-
If no REPL is running, start one:
lein repl :headlessWait for
.nrepl-portto appear. -
Evaluate small forms with
clojure_eval.- Prefer returning data (maps, vectors, strings) over printing.
requireornsload the namespace first if needed.
-
Repair before writing — when generating multi-line Clojure code, pass it through
clojure_repairfirst and only write the repaired output. -
Validate with the narrowest test command:
./lein test :only <namespace> ./lein test :with <subsystem>
Namespace discipline
- Evaluate the
nsform orrequirethe namespace before calling vars from it. - Use fully-qualified vars when moving between namespaces would add confusion.
- Prefer
userfor one-off setup and small probes. - Avoid mutating production namespaces during exploration; use scratch namespaces or small pure probes.
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 · 90 lines · 53 tokens per session scan A 708d7ce91455
clojure-repl is a skill published in the GitHub repository zcaudate-xyz/foundation-base (42 stars, last pushed 9d ago), licensed MIT. It adds 53 tokens to every session and 823 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-09-02.
Other skills, from other repositories
erlang-otp-behaviors
Use when oTP behaviors including genserver for stateful processes, genstatem for state machines, supervisors for fault tolerance, genevent for event handling, and building robust, production-ready Erlang applications with proven patterns.
omh-rust
This is an OMH rust workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
axiom-concurrency
Use when writing ANY async code, actors, or threads in an Apple-platform app, or seeing ANY concurrency error. Covers Swift 6 concurrency, @MainActor, Sendable, data races, async/await patterns.
haskell-pro
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
splitting-oversized-modules
Split an oversized Python module (a thousand-plus-line logic.py, models.py, api.py, or its test file) into a package of one module per concern, mechanically and provably without changing behavior. Use on a request to split / break up / decompose a god module or move functions out of one, once a human has agreed to…
migrate-better-result-3
Migrate a TypeScript codebase from better-result 2.x to 3.0. Use when upgrading better-result across the TaggedError syntax, removed Result serialization helpers, recovery inference, matching, or retry APIs.