Plugin marketplace for Clojure AI context in VS Code Copilot and Cursor: agents, skills, and workflows for REPL-first interactive programming with Calva Backseat Driver.
Note
Plugins contain agents and skills. Both types of content are lazy loaded by the agent, so they will not hurt your agents context window just by being there. They will only add some little description so that the agent knows when to load them.
The minimal starter-pack, IMO, is the clojure and clojure-editor plugins, and the clojure instructions. (There is some cross-referencing going on between these.) Also IMO, you need the babashka, and epupp, plugins.
| Plugin | Description | Contents |
|---|---|---|
| babashka | Babashka scripting and bb.edn task skills for idiomatic Babashka development. | Skills: babashka, babashka-tasks |
| clojure | REPL-first Clojure development — general agent and skill for any dialect and runtime; pairs with clojure-editor for safe edit delegation. | Agent: clojure · Skill: clojure |
| clojure-editor | Subagent for editing Clojure files using Backseat Driver structural editing tools. | Agents: non-clojure-editor, clojure-editor |
| epupp | Browser tampering and userscript development with Epupp (ClojureScript/Scittle in the browser). | Skill: epupp |
| squint | Squint ClojureScript development — compilation, REPL workflow, debugging, and tooling for squint.edn projects. | Skill: squint |
Instructions can't be bundled in plugins — install them separately:
| Instruction | Description | Install |
|---|---|---|
clojure |
Tiny. Nudge to help the Agent decide to load the Clojure skill |   |
Installation looks a bit different depending on platform. But your agent will know what to do. Give it the repo url and tell it what you want to have installed.
This repo will mature both in terms of its content and structure. Right now it is very raw and maybe not the easiest to contribute to (and certainly not to maintain). Please don't let that stop you from trying to contribute. 😀
Development happens on the next branch. Releases merge next into master (fast-forward only).
Copilot manifests under .github/plugin/ are the source of truth. Cursor manifests under .cursor-plugin/ are generated only — never edit them by hand.
# after changing .github/plugin/ manifests or plugin content
bb generate-cursor-plugins
bb validate
git add .github/plugin/ .cursor-plugin/bb validate runs Copilot checks plus Cursor validation (path resolution, frontmatter policy, and L4 drift detection against committed .cursor-plugin/ files).
Generated .cursor-plugin/marketplace.json and plugins/*/.cursor-plugin/plugin.json follow Cursor’s plugin reference. Install or test from the same git repo URL as Copilot; Cursor reads the generated tree, not .github/plugin/.
bb validateChecks Copilot and Cursor plugin structure: required fields, referenced paths, frontmatter identifiers, and regeneration fidelity.
bb publishThis runs bb validate first, then validates preconditions (on next, clean tree, ahead of master, changelog has unreleased entries), shows a summary, and on confirmation pushes a [publish] marker commit. CI validates again, runs ci-release (which regenerates both manifest trees), validates once more, commits Copilot and .cursor-plugin/ artifacts, tags, creates a GitHub Release, and merges next into master.
You are welcome to encourage my work, using this link: