How do I install the Aio Patch Setup skill?

Run npx skillmds@latest add aiocean/aio-patch-setup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Aio Patch Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aio Patch Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aio Patch Setup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aio Patch Setup?

aiocean (@aiocean) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aio Patch Setup by aiocean — Agent Skill

Name: Aio Patch Setup
Author: aiocean

Aio Patch Setup

Scaffold a new Claude-binary-patching project at CWD (or [target_dir]). Copies generic pipeline tools (extract/build/run, Python pipeline scripts, cli-nav AST navigator) + generic docs/guides into the target. Patches.json starts EMPTY — user fills it in; a reference example from the dirty-claude project is shipped beside it.

aiocean 4ceaa8b 47 files · 271.3 KB Updated Sep 17, 2026

File contents

aio-patch-setup — scaffold a new Claude-binary-patching project

Goal

Drop a complete, runnable patching pipeline into the target directory so the user can immediately:

Edit tools/pipeline/patches.json (start from empty schema or copy from patches.json.example)
Run /aio-claude-toolkit:aio-patch-extract to extract cli.js + natives from their installed claude
Run /aio-claude-toolkit:aio-patch-compile to apply patches + recompile a custom claude binary
Run /aio-claude-toolkit:aio-patch-run to exec the patched binary

What gets copied

Path	Source	User-owned?
`tools/extract.sh`	templates/tools/extract.sh (synced from dirty-claude + ARCH patch)	No — generic
`tools/build.sh`	templates/tools/build.sh	No — generic
`tools/run.sh`	templates/tools/run.sh	No — generic
`tools/pipeline/*.py`	dirty-claude pipeline (extract_cli, patch_cli, resolve_symbols, inline_sources, extract_native_modules)	No — generic
`tools/pipeline/patches.json`	EMPTY schema template	YES — user content
`tools/pipeline/patches.json.example`	dirty-claude pinned reference	No — reference
`tools/pipeline/sources/*.example`	dirty-claude reference patch body	No — reference
`tools/cli-nav/*.cjs`	AST navigator (acorn-based)	No — generic
`docs/*.md`	curated generic guides (anchor strategy, drift recovery, etc.)	No — generic
`.gitignore`	sensible defaults (dist/, .backup, pycache*/)	No — generic
`CLAUDE.md.example`	template for your project's CLAUDE.md	No — template
`README.md.example`	template for your project's README	No — template
`.aio-patch-setup` (hidden)	sync metadata (VERSION)	No — generated

NOT copied (opt-in via sibling skill): control/ — call /aio-claude-toolkit:aio-patch-control scaffold to install the reference HTTP control-channel sample.

Usage

/aio-claude-toolkit:aio-patch-setup [target_dir]

target_dir defaults to CWD.
FORCE=1 env var: overwrite generic scripts in an existing scaffold. Does NOT overwrite tools/pipeline/patches.json or tools/pipeline/sources/*.js (your patch content).

Next steps printed at end

After scaffold, prints:

Edit tools/pipeline/patches.json (start from patches.json.example if you want the dirty-claude HTTP control-channel patch body).
/aio-claude-toolkit:aio-patch-extract to extract cli.js.
/aio-claude-toolkit:aio-patch-compile to apply + build.
/aio-claude-toolkit:aio-patch-run to exec.

Implementation

The skill body invokes ${CLAUDE_PLUGIN_ROOT}/skills/aio-patch-setup/scripts/setup.sh "$@".

When invoked:

Resolves TARGET = $1 ?? $PWD
Guard: if $TARGET/tools/pipeline/ exists and FORCE is unset → exit 1 with hint
cp -r templates/tools + cp -r templates/docs + copy ancillary files into $TARGET/
Copy templates/VERSION → $TARGET/.aio-patch-setup (hidden — sync metadata for drift recovery)
Run check-deps.sh (warn-only)
Print "Next steps" hint

---name: aio-patch-setupdescription: Scaffold a new Claude-binary-patching project at CWD (or [target_dir]). Copies generic pipeline tools (extract/build/run, Python pipeline scripts, cli-nav AST navigator) + generic docs/guides into the target. Patches.json starts EMPTY — user fills it in; a reference example from the dirty-claude project is shipped beside it.---# aio-patch-setup — scaffold a new Claude-binary-patching project## GoalDrop a complete, runnable patching pipeline into the target directory so the user can immediately:1. Edit `tools/pipeline/patches.json` (start from empty schema or copy from `patches.json.example`)2. Run `/aio-claude-toolkit:aio-patch-extract` to extract cli.js + natives from their installed claude3. Run `/aio-claude-toolkit:aio-patch-compile` to apply patches + recompile a custom claude binary4. Run `/aio-claude-toolkit:aio-patch-run` to exec the patched binary## What gets copied| Path | Source | User-owned? ||------|--------|-------------|| `tools/extract.sh` | templates/tools/extract.sh (synced from dirty-claude + ARCH patch) | No — generic || `tools/build.sh` | templates/tools/build.sh | No — generic || `tools/run.sh` | templates/tools/run.sh | No — generic || `tools/pipeline/*.py` | dirty-claude pipeline (extract_cli, patch_cli, resolve_symbols, inline_sources, extract_native_modules) | No — generic || `tools/pipeline/patches.json` | **EMPTY schema template** | **YES — user content** || `tools/pipeline/patches.json.example` | dirty-claude pinned reference | No — reference || `tools/pipeline/sources/*.example` | dirty-claude reference patch body | No — reference || `tools/cli-nav/*.cjs` | AST navigator (acorn-based) | No — generic || `docs/*.md` | curated generic guides (anchor strategy, drift recovery, etc.) | No — generic || `.gitignore` | sensible defaults (dist/, *.backup, __pycache__/) | No — generic || `CLAUDE.md.example` | template for your project's CLAUDE.md | No — template || `README.md.example` | template for your project's README | No — template || `.aio-patch-setup` (hidden) | sync metadata (VERSION) | No — generated |**NOT copied** (opt-in via sibling skill): `control/` — call `/aio-claude-toolkit:aio-patch-control scaffold` to install the reference HTTP control-channel sample.## Usage```/aio-claude-toolkit:aio-patch-setup [target_dir]```- `target_dir` defaults to CWD.- `FORCE=1` env var: overwrite generic scripts in an existing scaffold. **Does NOT overwrite** `tools/pipeline/patches.json` or `tools/pipeline/sources/*.js` (your patch content).## Next steps printed at endAfter scaffold, prints:1. Edit `tools/pipeline/patches.json` (start from `patches.json.example` if you want the dirty-claude HTTP control-channel patch body).2. `/aio-claude-toolkit:aio-patch-extract` to extract cli.js.3. `/aio-claude-toolkit:aio-patch-compile` to apply + build.4. `/aio-claude-toolkit:aio-patch-run` to exec.## ImplementationThe skill body invokes `${CLAUDE_PLUGIN_ROOT}/skills/aio-patch-setup/scripts/setup.sh "$@"`.When invoked:1. Resolves `TARGET = $1 ?? $PWD`2. Guard: if `$TARGET/tools/pipeline/` exists and `FORCE` is unset → exit 1 with hint3. `cp -r templates/tools` + `cp -r templates/docs` + copy ancillary files into `$TARGET/`4. Copy `templates/VERSION` → `$TARGET/.aio-patch-setup` (hidden — sync metadata for drift recovery)5. Run `check-deps.sh` (warn-only)6. Print "Next steps" hint

Frequently asked questions