Use when launching, monitoring, or controlling AI coding agents (Claude Code, Codex, OpenCode, etc.) in tmux via Agent of Empires (aoe). Covers creating sessions, capturing agent output, running parallel worktree agents, and organizing work into groups and profiles. Prefer aoe over raw tmux for agent management.
SkillScore95Maintained
Automatic
◆AI Engineer pack
Last verified 9/1/2026
What it changes
Passed 21 of 22 test cases with the skill, and 3 of 22 without it.
Without skill14%
With skill95%
Checks it passed that the model alone missed
The response recommends aoe status -q
The response uses -c codex with aoe add
The response uses the -y flag with aoe add
and 18 more in the full report
19 fixed2 passed either way0 still failing1 broke
Pass-rate lift
+82 pp
Tokens
+54%
Agent turns
0%
Response time
-58%
Measured 9/1/2026v8 · latest is v1021 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/18/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
See it in action
One of 19 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 19
Prompt
I want to launch a session in the current directory titled 'codex-task' specifically using the 'codex' binary rather than default claude. What is the CLI invocation?
What was checked, without and with the skill
Checked
Without skill
With skill
The response uses -c codex with aoe add
Missed
Passed
case-09 · gemini-3.6-flash · 9/1/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md288 linessingle file
Agent of Empires (aoe) Skill
Use aoe to create, manage, and monitor AI coding agent sessions (Claude Code, Codex, OpenCode, etc.) in tmux. Prefer aoe over raw tmux commands for agent management.
When to use this skill
Launching one or more AI coding agents on project directories
Monitoring agent progress (waiting vs running vs idle)
Capturing agent output for review
Organizing agents into groups or profiles
Setting up parallel worktree-based development
Do NOT use this skill for general tmux window/pane management unrelated to coding agents.
Core concepts
Session: An agent process running in a tmux session. Each session has an ID, title, tool (e.g. claude), and project path.
Group: A named folder for organizing sessions (supports nesting with /, e.g. backend/api).
Profile: A separate workspace with its own sessions and config. Use -p <name> globally or set AGENT_OF_EMPIRES_PROFILE.
Status: One of running, waiting, idle, stopped, error, starting, unknown.
Command reference
Adding sessions
# Add a session for the current directory
aoe add . -t "my feature"
# Add with group, launch immediately
aoe add /path/to/repo -t "API work" -g backend -l
# Add with specific tool
aoe add . -t "codex session" -c codex
# Add in a git worktree on a new branch, YOLO mode (omit -b to check out an existing branch)
aoe add . -t "fix-123" -w fix/issue-123 -b -y -l
# Base the new branch on another branch instead of the default
aoe add . -t "fix-124" -w fix/issue-124 -b --base-branch fix/issue-123 -l