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 iwillig/clojure-system-prompt --skill clojure-repl-devgit clone --depth 1 https://github.com/iwillig/clojure-system-promptWrote 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/iwillig/clojure-system-prompt/clojure-repl-dev)<a href="https://agentmods.dev/skills/iwillig/clojure-system-prompt/clojure-repl-dev"><img src="https://agentmods.dev/badge/skills/iwillig/clojure-system-prompt/clojure-repl-dev/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/iwillig/clojure-system-prompt/clojure-repl-dev"><img src="https://agentmods.dev/badge/skills/iwillig/clojure-system-prompt/clojure-repl-dev.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.00067 | $0.01621 |
| Opus 5.5 | $0.00027 | $0.00648 |
| Sonnet 5.5 | $0.00013 | $0.00324 |
| Haiku 4.5 | $0.00007 | $0.00162 |
Grade A, and why
clojure-repl-dev 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clojure REPL-Driven Development
Core Workflow
Never write code without REPL validation.
Every coding task follows this loop:
- Gather context
- Take action
- Verify output
Before modifying any file:
- Read existing code - Use
readto examine target file and related files - Verify nREPL connection - Test:
clj-nrepl-eval -p 7889 "(+ 1 1)" - If connection fails, discover ports -
clj-nrepl-eval --discover-ports - Initialize dev environment if available -
clj-nrepl-eval -p 7889 "(fast-dev)" - Explore unfamiliar functions -
clj-nrepl-eval -p 7889 "(clojure.repl/doc function-name)" - Test in REPL - Define and validate functions before saving
- Check edge cases - nil, empty collections, invalid inputs
- Save only after validation - Use
editorwrite - Reload before verifying edits -
clj-nrepl-eval -p 7889 "(require '[project.core] :reload)" - Do not report success before verification - changed functions and relevant tests must pass
If nREPL fails, first run clj-nrepl-eval --discover-ports to find existing servers. Only ask the user to start a server if none are found.
If fast-dev is unavailable, continue without it.
Agent Loop
Use this loop for every coding task:
- Gather context - Read the target file, related code, call sites, dependencies, and tests
- Take action - Make the smallest focused change that solves the task; avoid unrelated refactors
- Verify output - Reload affected namespaces, test changed functions, validate edge cases, and run relevant tests
If verification fails, return to gather/action and fix the problem before reporting success.
Failure Recovery
If REPL evaluation, test execution, or namespace loading fails:
- Read the exact error message
- Isolate the failing expression or function
- Fix the root cause
- Reload affected namespaces
- Rerun verification
If delimiter errors occur, use clj-paren-repair instead of manual repair.
Task Communication
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 211 lines · 67 tokens per session scan A 98bf834fa1c4
clojure-repl-dev is a skill published in the GitHub repository iwillig/clojure-system-prompt (46 stars, last pushed 4mo ago), licensed MIT. It adds 67 tokens to every session and 1,621 once invoked, about $0.0003 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 skills, from other repositories
dotnet-reverse
A guide for analyzing compiled .NET and C# programs, including managed Windows executables and libraries. Reverse engineering means studying compiled software to understand how it works, and decompiling turns it back into readable approximate source code.
dart-run-static-analysis
Execute dart analyze to identify warnings and errors, and use dart fix --apply to automatically resolve mechanical lint issues. Use during development to ensure code quality and before committing changes.
agents-sdk-dotnet-debugging
Use when troubleshooting an agent built with the Microsoft Agents SDK (Microsoft.Agents.Hosting.AspNetCore and related packages) in C# / .NET. Trigger on any of these symptoms: build or C# compile errors, crashes on startup, 401 or auth errors on incoming requests, the bot not responding to messages, appsettings.json…
memory-optimization
Optimize Python code for reduced memory usage and improved memory efficiency. Use when asked to reduce memory footprint, fix memory leaks, optimize data structures for memory, handle large datasets efficiently, or diagnose memory issues. Covers object sizing, generator patterns, efficient data structures, and memory…
prismer-python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
golang-error-handling
Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log…