Experimental testing harness lives under experiments/claude-probe/.
A curated collection of 44 Claude Code plugins providing 400+ skills and 21 agents for development workflows.
The same skills, subagents and safety hooks also run in OpenCode, pi and Antigravity CLI. Skills are read in place from a checkout of this repo, so a skill edit reaches every harness without a copy step; subagents and hooks are exported to each tool's own format. Browse everything in the plugin catalog.
| Harness | Skills | Subagents | Safety hooks |
|---|---|---|---|
| Claude Code | Native plugin marketplace | Native | Native |
| OpenCode | Skill adapter: a search_skills tool plus the top 5 matches injected each turn |
Exported to OpenCode's agent format | Exported as OpenCode JS plugins |
| pi | Skill adapter (same as OpenCode) | Exported for @tintinweb/pi-subagents |
Run by a generated pi extension |
| Antigravity CLI | Plugin skill dirs registered in place in skills.json |
Exported to agents/<name>/agent.md |
Run by a generated hooks.json runner |
OpenCode and pi both read SKILL.md unmodified, but neither budgets its skill
listing: listing 382 skills natively measured ~34,000 tokens of context on
every turn (2026-08-24). The adapter
(ADR-0022,
adapters/) reaches all of them for ~600.
Add the marketplace, then install the plugins you want:
claude plugin marketplace add laurigates/claude-plugins
claude plugin install git-plugin@laurigates-claude-plugins
claude plugin install python-plugin@laurigates-claude-pluginsInside a session, /plugin browses and installs the same plugins.
Needs a clone of this repo, bun and just:
git clone https://github.com/laurigates/claude-plugins && cd claude-plugins
(cd adapters && bun install)
just setup-opencodesetup-opencode installs the subagents and hook plugins into
~/.config/opencode and writes an opencode.json that registers the adapter
for a local MLX model. An existing opencode.json is kept (a sample is written
beside it); wire the adapter into it with just oc-adapter-register. Details:
docs/opencode-export.md.
Needs a clone of this repo, bun and just:
git clone https://github.com/laurigates/claude-plugins && cd claude-plugins
(cd adapters && bun install)
just setup-pisetup-pi registers the adapter in ~/.pi/agent/settings.json, installs the
subagents and the safety-hook extension, and prints the steps to serve a local
model. just pi-adapter-unregister reverses the registration. Details:
docs/pi-export.md.
Needs a clone of this repo, just and Python 3:
git clone https://github.com/laurigates/claude-plugins && cd claude-plugins
just setup-antigravitysetup-antigravity adds each plugin's skills/ directory to
~/.gemini/config/skills.json, and installs the subagents and the safety-hook
runner into ~/.gemini/config. Existing entries in skills.json and
hooks.json are kept. just unconfigure-antigravity removes the skill
registrations, and just agy-check reports what is installed. Details:
docs/antigravity-export.md.
- Install the plugins for your harness, above
- Run a health check —
/health-plugin:health-checkthen/health-plugin:health-auditto diagnose your setup and get plugin recommendations for your stack - Follow the tiered setup — The Plugin Map provides a recommended install order (Tier 0 foundation through Tier 3+ stack-specific), decision trees, and project presets
For MCP servers, /configure-plugin:configure-mcp sets them up interactively.
The methodology behind these plugins — what a probabilistic agent should decide versus what a deterministic substrate should verify and remember. See docs/PRINCIPLES.md for the full set, each grounded in the rules, skills, and hooks that embody it.
- Bash 5+ — Required for shell scripts. macOS ships Bash 3.2; install via
brew install bash.
Discussions is the place to ask things in the open:
| Category | For |
|---|---|
| Q&A | How do I do X, why does a skill behave this way, is Z supported |
| Ideas | A plugin or skill you would like to exist, before it is a concrete request |
| Show and tell | What you built with these plugins |
Use issues for a defect or a concrete feature request, and please do not open a pull request just to ask a question.
Plugins use release-please for automated versioning. Use conventional commits to trigger releases:
feat(git-plugin): add worktree support # minor bump
fix(python-plugin): handle empty venv # patch bumpSee CLAUDE.md for detailed development instructions.
MIT