openspace
Ships with ai-rig: Practical agent workflows for Python, ML, and open-source maintenance. AI-Rig turns recurring work—scoping a change, reproducing a bug, reviewing a pull request, running an…
Claude Code
> /plugin marketplace add Borda/AI-Rig
Codex
$ claude plugin marketplace add Borda/AI-Rig
Cursor
$ claude plugin marketplace add Borda/AI-Rig
Gemini CLI
$ claude plugin marketplace add Borda/AI-Rig
GitHub Copilot
$ claude plugin marketplace add Borda/AI-Rig
OpenCode
$ claude plugin marketplace add Borda/AI-Rig
Windsurf
$ claude plugin marketplace add Borda/AI-Rig
Security report
Not enough data
Known flaws
Not published
Signed build
Not published
Maintained
Nov 14, 2026
Last push
Licence
Apache-2.0
Runs as
Local process
On your machine
Deprecated
Not published
Signals from public registries, not an audit. Checked Nov 15, 2026.
ai-rig README
🏠 Borda's AI-Rig

Practical agent workflows for Python, ML, and open-source maintenance. AI-Rig turns recurring work—scoping a change, reproducing a bug, reviewing a pull request, running an experiment, or checking release readiness—into explicit workflows with specialist ownership, evidence gates, and reviewable artifacts.
Eight packages serve three runtimes: six marketplace plugins for Claude Code, three for Codex, and one npm plugin for OpenCode, with codemap-py and bridge_CC-Codex shared by two hosts each.
Design principles:
- Simple and reliable: favor workflows that complete the user's goal, recover from routine problems, and reuse valid evidence.
- No silent blockers: routine incomplete handoffs and self-created blockers are defects to fix. Genuine permission, prerequisite, and user-decision boundaries stay explicit, with safety and verification intact.
- Root cause, not symptom: establish the cause with evidence and a falsification check before changing behavior. If it is unproven, keep investigating.
- Verified fixes: a fix is complete only after the original failure and affected sibling workflows are verified.
Contents
- Start here
- What this setup enables
- Complete capability map
- How it fits together
- Install for Claude Code
- Install for Codex
- Install for OpenCode
- What each plugin solves
- Practical workflow sequences
- How the packages compose
- Optional integrations and add-ons
- Artifacts and evidence
- Current boundaries
- Repository checkout and synchronization
- Upgrade and remove
- Troubleshooting
- Articles
- Documentation map
- Contributing
⚡ Start here
Choose the smallest plugin that solves the job in front of you. Every package installs independently; optional integrations add specialist depth or structural context without becoming hidden prerequisites.
| Need | Start with | What it gives you |
|---|---|---|
| Keep Claude agent configuration, routing, and reusable guidance healthy | 🏭 foundry | 10 specialist agents, 11 configuration/content skills, rules, hooks, audit, and calibration |
| Triage GitHub work, review PRs, resolve feedback, and prepare releases | 🌱 oss | 4 agents and 5 maintainer skills with human-reviewed replies and no automatic publish step |
| Plan, build, fix, refactor, debug, or review Python changes | 🛠️ develop | 6 validate-first development workflows plus setup, with reproduction/demo/safety-net gates |
| Plan and run literature-grounded ML experiments | 🔬 research | 2 research agents and 10 skills for planning, judging, running, verifying, ablation, retrospectives, and Kaggle notebooks |
| Answer import, caller, coupling, rename, and affected-test questions | 🗂️ codemap-py | The same 6 structural-analysis skills for Claude Code and Codex, backed by a local static Python index |
| Use evidence-first workflows and specialist role cards in Codex | 🤖 Codex Rig | 13 workflow skills, 1 lifecycle manager, 15 role cards, shared gates, calibration, and artifact contracts |
| Run evidence-first workflows, gates, and Git guardrails in OpenCode | ⚡ OpenCode Rig | 11 workflow skills, 7 evidence tools, 7 role agents, an adversarial loop, and an npm-installable TypeScript package |
| Hand bounded implement, advise, and review calls between the two hosts | 🌉 bridge_CC-Codex | 3 bridge verbs in both directions with explicit models, effort, budgets, compact envelopes, and recursion safety |
If you use Claude Code, read the Claude guide. If you use Codex, read the Codex guide. OpenCode installs the npm package directly; its README is the host guide.
🎯 What this setup enables
Show the evidence-first value of the full suite
- A bounded route from uncertainty to evidence: Foundry audits configuration and routing, Develop gates Python changes, OSS organizes maintainer work, Research keeps experiments reviewable, Codemap-py supplies static structure, and Codex Rig and OpenCode Rig provide the host-native workflow layer for Codex and OpenCode.
- Scope-selected specialist review: OSS and Codex Rig use narrow context packs and mandatory QA/challenge coverage where their contracts require it; smaller or lower-risk work can stay on the parent path.
- Review-to-remediation continuity: OSS and Codex Rig save findings as artifacts, ask which work to select, group related findings, and verify the selected closure rather than silently applying every comment.
- Validate-first development: Develop's feature path requires a failing demo, its fix path requires a failing regression test, and its refactor path protects current behavior before editing.
- Metric-guarded research: Research proposes one scoped change, measures the configured metric and guard, keeps improvements, and reverts regressions as auditable Git history.
- Calibration and recovery: Foundry and Codex Rig measure workflow/instruction quality, confidence, and known leaks; those results improve the process but do not guarantee model correctness.
These are workflow contracts, not promises that every run launches every specialist, finds every dynamic dependency, or publishes a correct change. The linked plugin READMEs define each route's prerequisites, fallback, and stop behavior.
🔧 Complete capability map
This is the literal shipped skill inventory. The host guides list every agent, role, rule, and hook; the plugin READMEs document arguments, outputs, prerequisites, recovery, and edge cases.
Show complete capability map
| Package | Complete skill roster |
|---|---|
| 🏭 Foundry | /foundry:setup, /foundry:audit, /foundry:calibrate, /foundry:manage, /foundry:brainstorm, /foundry:investigate, /foundry:profile, /foundry:distill, /foundry:session, /foundry:create, /foundry:humanizer |
| 🌱 OSS | /oss:analyse, /oss:review, /oss:resolve, /oss:release, /oss:setup |
| 🛠️ Develop | /develop:plan, /develop:feature, /develop:fix, /develop:refactor, /develop:debug, /develop:review, /develop:setup |
| 🔬 Research | /research:topic, /research:plan, /research:judge, /research:run, /research:sweep, /research:verify, /research:fortify, /research:retro, /research:kaggle, /research:setup |
| 🗂️ Codemap-py | scan-codebase, query-code, test-impact, rename-refs, integration, debrief-coding, namespaced as /codemap-py:... in Claude Code and $codemap-py:... in Codex |
| 🤖 Codex Rig | $codex-rig:assess, $codex-rig:audit, $codex-rig:calibrate, $codex-rig:code-remediate, $codex-rig:code-review, $codex-rig:implement, $codex-rig:investigate, $codex-rig:kaggle, $codex-rig:manage, $codex-rig:optimize, $codex-rig:release, $codex-rig:research, $codex-rig:sync, $codex-rig:agent-shims |
| ⚡ OpenCode Rig | /rig-plan, /rig-investigate, /rig-research, /rig-implement, /rig-review, /rig-remediate, /rig-challenge, /rig-optimize, /rig-distill, /rig-release, /rig-doctor |
More MCP servers from other plugins.
Questions about openspace.
- Which coding agents can use openspace?
- openspace works in any agent that reads an MCP config file: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf. Each agent reads it from its own file; this page names the file for each one.
- How do I add openspace to Claude Code?
- Run this in claude code: /plugin marketplace add Borda/AI-Rig

