Skill Detail

Run multi-harness coding-agent sessions with Claudexor

Use Claudexor as a local-first control plane for Codex, Claude Code, Cursor, OpenCode, Antigravity, and API-backed coding harnesses with quotas, races, review gates, and durable evidence.

Developer ToolsMulti-Framework
Developer Tools Multi-Framework Security Reviewed
⭐ 472 GitHub stars ⬇ 1.2k/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill run-multi-harness-coding-agent-sessions-with-claudexor Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Node.js 20.19+, pnpm, Git, one or more supported vendor CLIs or provider API keys
Install & setup
Install with npm install -g claudexor, run claudexor doctor, then connect Codex, Claude Code, Cursor, OpenCode, Antigravity, or API credentials before starting repository-bound runs.
Author
razzant
Publisher
Open Source
Last updated
Sep 19, 2026
Quick brief

Use Claudexor when an operator needs one local control plane for several coding-agent harnesses. The workflow is to install Claudexor, connect the vendor CLIs or API keys that are already authorized for the operator, run repository work through typed turns, compare harness outputs, track quota and cost signals, and keep resulting changes as inspectable patches or file manifests.

How it works

What this skill actually does

When to use it

Invoke this skill when a coding task benefits from multiple agent harnesses, quota-aware routing, independent review, or deterministic gates around file edits and command execution. It is useful for teams that already use Codex CLI, Claude Code, Cursor, OpenCode, or Antigravity and want a repeatable orchestration layer without moving work into a hosted black box.

Scope boundary

This is not a generic AI orchestration framework listing. Keep the workflow bounded to local coding-agent execution: harness login, workspace selection, read/write turns, races, reviews, quota accounting, protected paths, and evidence capture. Do not use it as a general model gateway or replacement for application runtime orchestration.

Operator checklist

  • Install the CLI and run the doctor check.
  • Connect at least one supported vendor CLI or provider API route.
  • Bind the run to a concrete repository or remote SSH workspace.
  • Choose the harnesses, budget limits, protected paths, and review gates.
  • Inspect patches, receipts, cost/quota facts, and review output before applying changes.