# Crack Setup

Configure or change the approved worker models for codex-on-crack, inspect available...

- Repository: https://github.com/ethanplusai/codex-on-crack (784 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-03
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add ethanplusai/codex-on-crack --skill crack-setup -g -a claude-code -y`
Codex: `npx skills add ethanplusai/codex-on-crack --skill crack-setup -g -a codex -y`
Cursor: `npx skills add ethanplusai/codex-on-crack --skill crack-setup -g -a cursor -y`
Gemini CLI: `npx skills add ethanplusai/codex-on-crack --skill crack-setup -g -a gemini-cli -y`

## Description

Configure or change the approved worker models for codex-on-crack, inspect available models and compatibility, preview role files, or undo a setup. The user selects the lead in Codex. Setup preserves root settings, credentials, unrelated agents, and config.toml.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Choose workers; preserve the lead

Helpers live in `../crack/scripts/`. Keep the user's existing model/provider
choices. Installing skills alone does not configure workers or change the lead.

1. Run `node ../crack/scripts/setup.mjs scan` with the session's home/profile.
   Show relevant eligible models, efforts, image support, context, and exclusions.
   Catalog presence is not account access or a working provider route. Do not
   rank capabilities the catalog does not establish or invent prices.
2. Read an existing `crack.toml` before proposing changes. Start with one builder
   chosen by the user. Additional roles can map to `implementation`, `ui`,
   `review`, `research`, or `tests` with a `tasks` array. These are user preferences,
   not demonstrated model strengths. Set the exact model and a supported effort;
   keep fallback optional. Never change the selected lead to make setup pass.
3. Write a draft in a task-owned directory. Preview with
   `node ../crack/scripts/setup.mjs plan --roles DRAFT` and show the concrete
   model/effort and file changes. Apply the agreed configuration with
   `node ../crack/scripts/setup.mjs apply --roles DRAFT`. If the specific model
   choices or global writes aren't yet authorized, obtain that decision after
   producing the preview. Don't repeat approval already given for those choices.
4. Return the receipt path and explain that a fresh client session must load the
   generated native roles. Run `doctor.mjs`; then use a real authorized task to
   verify child metadata. No paid installation smoke test is needed.

Draft shape (replace the model with an exact eligible ID):

```toml
schema_version = 1
[roles.builder]
model = "MODEL_FROM_SCAN"
writes = true
tasks = ["implementation", "tests"]
brief = "Implements the scoped task and verifies it for lead review."
```

The rest: https://github.com/ethanplusai/codex-on-crack/blob/HEAD/plugins/codex-on-crack/skills/crack-setup/SKILL.md