gremllm-plugins

A family of small tools for coding agents, each packaged on its own.

These tools open no network connection: no telemetry, no uploads, nothing reported back to us. What they produce stays on your disk. They do run inside a coding agent, so whatever you hand the agent still reaches your LLM provider, as it already does.

Plugins

• gremllm-doc/ — turn a markdown document into one self-contained HTML file that a reviewer opens locally, comments on, saves, and sends back.
• gremllm-handoff/ — carry a strategic document round between people working through coding agents; starts with provenance-delta, which keeps dated artifacts named, framed, and honest about their provenance.

Install

The only prerequisite is Node — nothing to install or build.

Claude Code

/plugin marketplace add quantisan/gremllm-plugins
/plugin install gremllm-doc@gremllm
/reload-plugins

Then /gremllm-doc:export in any project turns a doc into a review artifact.

• Pick User scope when prompted, so the skill works in every project, not just the one you installed it from.
• marketplace add clones over SSH by default. If you don't have a GitHub SSH key set up, set CLAUDE_CODE_PLUGIN_PREFER_HTTPS=1 first.
• Claude Code shows a one-time trust warning before installing — plugins can run code.

OpenCode

Clone the repo, then name its absolute path in the plugin array of ~/.config/opencode/opencode.json:

git clone https://github.com/quantisan/gremllm-plugins.git

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["/absolute/path/to/gremllm-plugins"]
}

Restart OpenCode. One entry installs every plugin's skills — ask for a skill by name ("use the export skill", "use the provenance-delta skill") or describe the job and let the agent pick it up. To update, git pull in the clone and restart OpenCode.

• The path must be written out absolute — OpenCode does not expand ~/ in plugin entries.
• Don't use the name@git+https://... install form some plugins document: current OpenCode (v1.18.x) fails those installs silently.

Working in this repo

npm install              # once, from the root — installs every plugin's dependencies
npm test --workspaces    # run every plugin's suite

Most other commands run inside the plugin's own directory. Export is the exception: run it from the repo root, so the paths you type resolve against your own working directory rather than the plugin's.