メニュー
Initialize the standard Interlateral two-agent CLI mesh from a bootstrap agent by running me.sh, launching Claude Opus 4.7 plus Codex 5.5, proving live ACK, and waiting for "Reporting for Duty!". The bootstrap agent is not part of the mesh.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | init |
| description | Initialize the standard Interlateral two-agent CLI mesh from a bootstrap agent by running me.sh, launching Claude Opus 4.7 plus Codex 5.5, proving live ACK, and waiting for "Reporting for Duty!". The bootstrap agent is not part of the mesh. |
| metadata | {"owner":"interlateral","version":"1.0","weight":"light"} |
| compatibility | Bootstrap operator with shell access to this repo, tmux, claude, codex, and node. |
Use this skill when a fresh bootstrap agent is asked to initialize the normal Interlateral CLI mesh.
This skill starts exactly the standard duo:
ia-claudeia-codexIt does not launch Gemini CLI, Antigravity CLI, Antigravity Desktop, desktop inbox peers, or extra workers. Those peers are opt-in only when Principal Human explicitly selects them outside the standard init flow.
The agent running this skill is the bootstrap operator. It is not a mesh peer and should not claim a mesh identity.
Do not use this skill for:
For desktop peers, use desktop-mesh-peer.
For transport details, live comms mechanics, ACK proof, direct-send rules, and troubleshooting, use mesh-comms-core.
For quartet work, use ready-rock-quartet.
init is the normal CLI bootstrap entrypoint. It also orients operators to the rest of the live-comms skill map: desktop-mesh-peer for Claude Desktop or Codex Desktop, and mesh-comms-core for the shared tmux/direct-injection substrate.
me.sh owns the launch mechanics and prints the exact commands before starting the sessions.
Defaults:
claude-opus-4-7gpt-5.5Reporting for Duty!/tmp/interlateral-agents-tmux.sockModel and argument defaults are configurable with environment variables:
CLAUDE_MODEL=claude-opus-4-7 CODEX_MODEL=gpt-5.5 ./me.sh
CLAUDE_ARGS="..." CODEX_ARGS="..." ./me.sh
cd path/to/interlateral_agents
./me.sh
Use ./me.sh --force only when the human explicitly accepts replacing attached ia-claude or ia-codex windows.
Confirm it prints:
Reporting for Duty!
tmux -S /tmp/interlateral-agents-tmux.sock list-sessions
tail -40 interlateral_dna/comms.md
The comms log should contain a stamped Claude ACK to Codex and a stamped Codex ACK to Claude.
If startup fails:
interlateral_dna/claude_telemetry.log and interlateral_dna/codex_telemetry.log.source scripts/tmux-config.sh
run_tmux kill-session -t "$CC_SESSION" 2>/dev/null || true
run_tmux kill-session -t "$CODEX_SESSION" 2>/dev/null || true
Do not use scripts/shutdown.sh for this scoped cleanup. That script intentionally tears down every session on the shared socket.
Do not improvise new mesh topology inside this skill. Escalate if the standard duo cannot boot cleanly after one controlled retry.
When complete, report:
INIT_STATUS: READY
BOOTSTRAP_AGENT_IN_MESH: no
SOCKET: /tmp/interlateral-agents-tmux.sock
CLAUDE_SESSION: ia-claude
CODEX_SESSION: ia-codex
READY_PHRASE: Reporting for Duty!
ACK_STATUS: direct plus ledger confirmed
Coordination guidance for the narrow case of multiple desktop-backed agents active concurrently in the same desktop-backed coordination context. Use ONLY when two or more desktop peers are running at the same time; normal CLI agents and single desktop peers should ignore this skill. Read this BEFORE concurrent desktop-to-desktop handoffs to keep sender labels unique, identity routing cooperative, and material handoffs proven.
Mandatory near-live communication discipline ("the Law") for the two DESKTOP agents (claude-desktop and codex-desktop) on the Interlateral mesh. Read this BEFORE any desktop-to-desktop peer communication, peer-superset, ready-rock-quartet, sprint-overseer, gate-keeper, sprint handoff, or substantial delegation. It forces correct live comms and prevents the recurring failure modes. Normal CLI agents, Warp/terminal peers, and single non-desktop workflows should ignore this skill and use the ordinary repo protocols.
Join the Antigravity CLI (agy, Gemini 3.5 Flash) to the Interlateral mesh as a native CLI peer with its own tmux session, identity stamping, and the agy.js send helper. Use this instead of the Antigravity desktop-app CDP path.
Run a two-agent proxy approval council for autonomous sprint gates. Use when a sprint needs delegated approval for human gates such as deploy, live mutation, push, cleanup, skip, or shortened watch decisions, while requiring two independent agents to reach consensus that the human principal would approve under written policy and preferences.
Operate or troubleshoot Interlateral CLI mesh transport: tmux socket discovery, direct-send helpers, comms.md ledger, identity stamping, idle checks, ACK proof, and safe prompt injection. This is comms mechanics only, not a collaboration workflow.
Run a two-agent independent review/redteam followed by peer collaboration to produce a consensus superset of findings and enumerated revision requests. Use when Codex 5.5 and Claude Opus 4.7 should first critique a matter independently, then exchange work, synthesize the best combined analysis, and finish with a single agreed revision list.