Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Claudex: CEO Harness for Claude Code

    2

    A CEO harness for Claude Code to route, delegate, and verify work across all your repositories from one session.

    $15

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Claudex: CEO Harness for Claude Code

    Claudex: CEO Harness for Claude Code

    Example session with this skill installed

    /delegate my-api "Add a health check endpoint at /health that returns 200 OK"

    • Read your context and instructions
    • Compiled the claudex

    I have routed this request to the my-api project and initialized a new delegation flow.

    Task Delegation: T-1024

    The task has been created in the ledger and a headless worker has been dispatched. I will monitor the process until git evidence is produced.

    FieldValue
    Task IDT-1024
    Projectmy-api
    Statusdispatched
    Worker TypeHeadless (claude -p)
    Permission Modeallowed_tools
    Verification GateGit commit + npm test

    Directive sent to worker:

    Implement a new GET /health endpoint. It must return a 200 OK status. Follow existing Express controller patterns in src/routes/. Ensure a unit test is added in test/routes.test.js and passes. Commit as feat: add health check endpoint.

    Next steps

    • Wait for the worker to finish; I will notify you when the review gate is ready.
    • Use /sweep to check the status of this and other active background tasks.
    • View the full task requirements at ledger/tasks/T-1024.md.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Managing multiple repositories often leads to context switching, untracked agent runs, and unverified code changes. Claudex solves this by turning a single Claude Code session into a "CEO harness" that centralizes project management, routes work to specific repos, and delegates tasks to headless workers.

    What it does

    • Multi-project Routing routes requests to the correct repository based on a central registry.
    • Headless Dispatch executes work in background claude -p sessions to keep your main terminal free.
    • Evidence-based Tracking closes tasks only when git commits, changelogs, or tests prove completion.
    • Engineering & Marketing Doctrine applies specialized CTO/CMO playbooks to ensure high-quality code and safe content.
    • Automated Reconciliation walks the ledger to find stalled tasks or unrecorded work via ground-truth git logs.

    How it works

    1. Initialize the harness in a central directory to create your project registry and task ledger.
    2. Onboard existing git repositories to define their "trust dial" and allowed bash tools.
    3. Delegate work by creating a ledger task, which triggers a headless worker in the target repo.
    4. Verify results through automated review gates before the CEO session marks the task as done.

    Frameworks & tools

    This skill integrates with the claude CLI, git, bash, jq, and optionally Codex CLI for multi-model deliberation.

    Why this beats prompting it yourself

    Manual prompting across repos leads to "hallucinated progress" where agents claim tasks are done without committing code. Claudex enforces a hard split between the "deciding" CEO and "executing" worker, ensuring every action is recorded in a tamper-evident ledger.

    Use cases

    • Manage 10+ active repositories from a single unified command interface.
    • Run multi-model "Fusion" panels to stress-test architectural decisions before implementation.
    • Automatically generate project backlogs based on recurring defect classes and skipped tests.
    • Gate autonomous marketing drafts to ensure brand safety and human approval.

    Known limitations

    Requires a local environment with bash and the claude CLI installed. Workers are limited by the allowed_tools defined in each project's dossier.

    Requires local bash, git, and jq. Headless workers are constrained by project-specific allowed_tools. Does not support non-git repositories.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 13 days ago

    Requires

    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed13 days ago

    What's inside

    Frequently Asked Questions

    Claudex acts as a central command layer for the Claude Code CLI, allowing you to manage, delegate, and track tasks across multiple repositories simultaneously without manual context switching.

    Yes, Claudex requires the Claude CLI (claude -p) to be installed locally, along with bash, git, and jq for automated ledger tracking and project routing.

    The 'Evidence-based Tracking' feature ensures tasks are only marked complete if the worker provides verifiable proof, such as a successful git commit, a passing test suite, or an updated changelog.

    You will receive the Claudex skill package, including the CEO harness scripts, the project registry templates, and the CTO/CMO doctrine playbooks for specialized task routing.

    Setup is simple: initialize the harness in a central directory, register your local repository paths, and define your 'trust dials' to specify which bash tools each project is allowed to access.

    Absolutely. The Headless Dispatch feature allows you to trigger tasks in background sessions, leaving your main terminal open for high-level strategy and oversight.

    New in Agents & Orchestration