Crack Plan

Community

ethanplusai

crack-plan

Start a substantial build with Codex on Crack. Inspect the user's own configured models and readiness, recommend a lead/worker/tool shape with reasons, and let the user decide before work starts. Use before delegating; keep small or solo tasks direct.

Overview

Publisher	ethanplusai
Repository	`codex-on-crack`
Skill name	`crack-plan`
Stars	752
Forks	73
Bundled files	2
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by ethanplusai on GitHub. Read the source before you install it.

Installation

Install the Crack Plan AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/ethanplusai/codex-on-crack/tree/main/plugins/codex-on-crack/skills/crack-plan
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/ethanplusai/codex-on-crack/tree/main/plugins/codex-on-crack/skills/crack-plan

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/ethanplusai/codex-on-crack.git /tmp/codex-on-crack
mkdir -p .claude/skills
cp -r /tmp/codex-on-crack/plugins/codex-on-crack/skills/crack-plan .claude/skills/crack-plan

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Crack Plan in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Crack Plan on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Crack Plan is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Plan one build, then choose

Use this when the user wants to start a meaningful build and has not already decided how to divide it. The goal is a short, honest plan built from what is actually configured, with the final choice left with the user.

Resolve named models before recommending

A request such as “run subagents through Opus 5.5” already selects a model. Follow the model-request routing in crack; the user need not specify the subscription or adapter. The native planner below does not inventory Claude Code access, so a missing native role is not proof that Opus is unavailable. Check the external adapter separately when requested. Keep route ambiguity, missing access, and unsupported model versions explicit.

Gather local facts only

Run node scripts/plan.mjs (add --task implementation|ui|review|research|tests when the work is known). It reads the model catalog Codex already uses, the generated roles, and static readiness. It makes no model call, changes no configuration, and never probes a provider.

Recommend with reasons, then let the user decide

When several configured workers qualify, offer the recommendation the planner returns and say why in its terms: a role whose configured tasks list includes this category, a conventional role name for the task, and a generated file that is present and unmodified. Label that as a qualitative judgement about fit, not a measured ranking, and accept a different choice without argument.

If the user already named a worker role or a mode, honor it: do not re-ask for a decision that is already made. If they named something that does not qualify, say exactly which requirement failed rather than substituting another model.

Keep the roles distinct

The Codex host model is whatever the user selected in the composer. A skill cannot change it.
A configured worker implements one bounded bundle and is reviewed.
The optional external project lead is a different thing: the official Claude Code client on an existing subscription login, on the exact model claude-opus-5-5, with no Codex tools and no API fallback. Read ../crack/references/external-lead.md before offering it.

Host-only solo work needs no worker. Explicit Opus implementation uses the external adapter's solo mode and its readiness checks. When no configured worker qualifies, say so and suggest $codex-on-crack:crack-setup; do not invent a substitute.

Hand off

Once the shape is agreed, hand the work to $codex-on-crack:crack with the chosen route and worker, or keep a host-only task direct. For replay of a host session and worker sessions, read ../crack/references/replay.md.

Keep the claims honest

Catalog presence is not account access, provider routing, or quality.
No allowance, quota, savings, or price claims. Missing usage stays unknown.
Terminal tooling is an allowlist, not filesystem isolation; scope follows the approved workspace and task.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB
scripts/plan.mjs12 KB

Frequently asked questions

What does the Crack Plan AI skill do?

Why use Crack Plan on TypingMind?

Because you install it once and use it with any model. Crack Plan is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Crack Plan in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ethanplusai/codex-on-crack/tree/main/plugins/codex-on-crack/skills/crack-plan. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Crack Plan?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Crack Plan?

As many as you like. As long as a model supports skills, you can use Crack Plan with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Crack Plan AI skill free?

Yes. It is published on GitHub by ethanplusai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Tavily

openclaw

OrganizationPopular

Tavily web search, content extraction, and research tools.

Deep Research

Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any…

Exa Search

Neural search via Exa MCP for web, code, and company research. Use when the user needs web search, code examples, company intel, people lookup, or AI-powered deep research with Exa's neural search…

Wayfinder

Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Plan one build, then choose

Resolve named models before recommending

Gather local facts only

Recommend with reasons, then let the user decide

Keep the roles distinct

Hand off

Keep the claims honest

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now