init-agents

Initialize tmux-based multi-agent routing and pane discovery for coding controllers.

55|10|Updated May 15, 2026
One-click install
npx skills add https://github.com/noho/code-is-cheap --skill init-agents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-agents
Source: https://github.com/noho/code-is-cheap/tree/main/skills/init-agents
Command: npx skills add https://github.com/noho/code-is-cheap --skill init-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of unreliable, misrouted multi-agent communication by standardizing how a controller discovers tmux panes, clears or preserves sessions safely, and sends correct handoff prompts to the right agent types.

Core Features & Use Cases

  • Agent routing map: Selects the right agent (Claude Code vs Codex) for review or implementation/fix work so prompts match expected capabilities.
  • Tmux pane discovery and targeting: Forces two-step discovery to obtain the correct full pane id before any send/wait/capture actions.
  • Safe session management: Uses clear only for new tasks and avoids clearing when the target pane is mid-assignment to prevent losing context.
  • Prompt formatting safeguards: Prevents tmux-send truncation by avoiding bare issue/PR number patterns like #45 and using safer alternatives.
  • Role-scoped handoff checklist: Ensures prompts include gate/scope/artifact/stop-condition and prohibits unintended commits, pushes, PRs, or gate transitions unless authorized.

Quick Start

Use init-agents to initialize the controller session so it can discover tmux panes for AgentMiMo, AgentDS, AgentGLM, AgentOpus, and AgentCodex and reliably dispatch review and implementation/fix handoffs.

Frequently Asked Questions about init-agents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate multi-agent tmux sessions for safe Claude Code and Codex handoffs?

You can orchestrate multi-agent tmux sessions by initializing deterministic agent routing, pane discovery, and safe session/handoff rules. This ensures prompts match agent capabilities for review or implementation work during gated workflows.

Why does tmux send truncate my issue numbers like #45 during agent handoffs?

Tmux send truncates bare issue or PR number patterns like #45. To prevent this truncation during prompt routing, you should use safer alternative formatting patterns when sending handoff prompts to agent panes.

What is the correct way to discover tmux panes before sending prompts to coding agents?

The correct way to discover tmux panes is a two-step identification process. You must obtain the correct full pane id before executing any send, wait, or capture actions to ensure prompts reach the intended agent.

How do I manage tmux sessions without losing context during mid-assignment agent tasks?

You manage safe tmux sessions by clearing panes only for new tasks and preserving them when the target pane is mid-assignment. This prevents losing context during implementation or fix work.

Can I use this multi-agent workflow orchestration for gated development with multiple coding agents?

Yes, this workflow orchestration is designed for gated development. It applies when you orchestrate review and implementation work across multiple Codex and Claude Code agents during handoff phases using role-scoped checklists.

What should a role-scoped handoff prompt include for deterministic multi-agent communication?

A role-scoped handoff prompt must include gate, scope, artifact, and stop-condition details. It prohibits unintended commits, pushes, PRs, or gate transitions unless explicitly authorized during the workflow.