yui-cc-plugins

Use when the user invokes `/token-report` or asks for an analytical summary of which compression plugin (rtk / headroom / caveman) is effective for which workload. Aggregates token-meter JSONL, `rtk gain`, and the active Claude Code session transcript, then produces recommendations.

Use when the user invokes `/token-clear` or asks to delete old token-meter JSONL logs by retention period. Confirms before destructive deletion.

Use when the user invokes `/token-stats` or asks for a token volume / compression-effect report across recent days. Aggregates JSONL records by tool and plugin into a single page summary.

Use when the user invokes `/token-plugins` or asks to list, install, enable, or disable a compression plugin (rtk / caveman / headroom). Wraps each plugin's enable/disable mechanism behind a unified interface.

Use when the user invokes `/token-measure` or asks to enable/disable the token-meter measurement system, list per-tool measurement state, or override a single tool. Provides ON/OFF control and JSONL-backed activity listing.

Orchestrate parallel execution of multiple tasks via cmux workspaces. Each task gets its own git worktree + Claude Code session. The parent session acts as orchestrator, monitoring all child sessions. Dynamically discovers available agent types from .claude/agents/ and passes the list to child sessions, which select the appropriate agent themselves. Supports three layout modes: workspace (default, separate sidebar entries), split (panes within current workspace), and claude-teams (native Agent Teams via cmux claude-teams). Dispatches immediately without parent-side planning — each child handles its own brainstorming/planning in parallel. Use when: "parallel execution", "team dispatch", "run these at once", "run these in parallel", "dispatch tasks", "execute these simultaneously", or when 2+ independent tasks need concurrent execution.

Bring up an isolated development stack per git worktree. Reserves a port slot from a shared registry, writes .env.dispatch, then starts all services declared in .dev-up.yaml (docker-compose stacks and/or direct commands like `go run`, `pnpm dev`). Spawned commands are tracked with PID/PGID for clean teardown. Use when verifying the running app inside a worktree spawned by cmux-team-dispatch-task, or whenever you need parallel stacks without port collisions. Run the `setup` subcommand once per new project to generate .dev-up.yaml.

Run agent-browser based E2E tests against the worktree-isolated stack brought up by dev-up. Reads .env.dispatch for URLs and uses --session <project>-<slot> so each worktree has its own browser context (cookies, storage, history). Scenarios are bash files in .e2e-scenarios/ written dynamically by the child Claude per ticket. Run `install` once to install agent-browser globally.

Activated when running as a cmux-team sub-agent. Triggers: .team/team.json exists AND current session was spawned by Conductor (detect via: initial prompt contains "[CMUX-TEAM-AGENT]" marker). Provides: output protocol, task creation, inter-agent coordination.

Use when orchestrating multi-agent development via cmux. Triggers: .team/ directory exists, user says "team", "spawn agents", "parallel", "sub-agent", or any /team-* command is invoked. Provides: agent spawning, monitoring, result collection, synchronization protocols.

cmux ターミナル内での操作スキル。ペイン分割、サブエージェント起動・監視・結果回収、コマンド送信、画面読み取り、通知に使用。CMUX_* 環境変数が存在する場合にトリガーされる。