/00. Claude Plugins

A Claude Code plugin is a folder of skills, agents, hooks, and slash commands that Claude installs per project. 28 plugins, 68 skills here.

/plugin marketplace add aiocean/claude-plugins
/plugin install <plugin-name>@aiocean-plugins

Skills load when their description matches your message, hooks fire on tool-call events, agents spawn on the Agent tool. Idle plugins cost nothing — browse plugins or read the guides.

Folders

Articles

/03. aio-patch-control

aio-patch-control

From plugin aio-claude-toolkit

Install

/plugin install aio-claude-toolkit@aiocean-plugins

aio-patch-control — HTTP control-channel reference + docs

Goal

Drop a working sample gateway into <project>/control/ so you can drive your patched claude binary over HTTP/SSE if your patches.json injects an HTTP server (the dirty-claude pattern). Also expose the protocol docs.

Usage

/aio-claude-toolkit:aio-patch-control scaffold     # copy sample scripts into ./control/
/aio-claude-toolkit:aio-patch-control docs         # print docs/control-channel.md
FORCE=1 /aio-claude-toolkit:aio-patch-control scaffold   # overwrite existing ./control/

What scaffold ships

  • control/simple-client.sh, raw-client.sh — minimal curl-based clients
  • control/stream-client.sh, stream-text.sh, stream-ambient.sh — SSE streaming variants
  • control/interactive-client.sh — line-oriented driver
  • control/client.ts — bun TUI (richer UX)
  • control/README.md — quick reference

Requires

  • Scaffolded project (walk-up sentinel) — your patches.json must inject an HTTP control-channel for these clients to actually talk to the binary
  • For bun TUI: bun installed

Implementation

Invokes ${CLAUDE_PLUGIN_ROOT}/skills/aio-patch-control/scripts/control.sh "$@".