Agi Super Team Sync

AGI Super Team Sync

Overview

Install AGI Super Team in two explicit layers:

1. A managed Musk CEO block in the user's global AGENTS.md, making the current Codex parent the CEO coordinator in every repository.
2. One or more outcome Teams backed by generated ast-* C-suite roles. CTO, CPO, and CCO may route to their optional specialist groups when installed.

The installer preserves content outside its managed block, never deletes unrelated agents, leaves config.toml unchanged, previews by default, and backs up replaced files.

Workflow

1. Resolve scripts/install_codex_team.py relative to the absolute directory containing this SKILL.md. Do not assume the current working directory is the Skill directory.

2. List the available Teams when scope is unclear:

   python3 "<absolute-skill-directory>/scripts/install_codex_team.py" --list-teams
   

3. Preview the smallest requested installation. For the global CEO and all outcome Teams:

   python3 "<absolute-skill-directory>/scripts/install_codex_team.py" --global-ceo --all-teams
   

   For one Team, replace --all-teams with --team solo-founder or another listed Team ID.

4. Summarize additions, updates, unchanged files, destination, and any AGENTS.override.md warning.

5. Because the user must explicitly request installation, only then append --install to the exact previewed command.

6. Report the backup directory when files were replaced. Tell the user to start a new Codex task; Codex loads global guidance and personal Agent TOMLs at task start.

To sync every bundled specialist Agent rather than an outcome Team, use the legacy all-Agent path:

python3 "<absolute-skill-directory>/scripts/sync_codex_agents.py"
python3 "<absolute-skill-directory>/scripts/sync_codex_agents.py" --install

To install only executive pyramids, use repeatable --with-subagents <manager-id> for any manager declared in agent-hierarchy.json, or --all-subagents for all 92 specialists. --with-cco-specialists remains a compatibility alias.

Safety Rules

• Never copy credentials, conversation databases, memory stores, config.toml, or unrelated local backups.
• Never delete destination files. Unrelated agents remain untouched.
• Preserve all content outside the AGI-SUPER-TEAM:CEO managed markers in global AGENTS.md.
• Refuse malformed markers, symlinked destinations, unsafe Codex homes, incomplete Team payloads, and unknown Team IDs.
• Keep the preview as the default. Use --install only when the user has authorized installation or synchronization.
• A custom destination may be supplied with --codex-home; validate it before use.
• Do not enable automatic hooks, daemons, or background memory capture.

Configuration

This Skill deliberately leaves ~/.codex/config.toml unchanged. Parent-led C-suite leaves work with depth 1. Manager-led specialists require depth 2; recommend reviewing settings such as:

[agents]
max_threads = 4
max_depth = 2
job_max_runtime_seconds = 1800
interrupt_message = true

Explain that depth 2 is a functional requirement only for an executive spawning its own specialists. Preserve existing settings and let the user decide before editing them; if depth remains 1, the parent CEO must dispatch the selected specialist directly and report that flat fallback honestly. With four threads, run one manager plus at most two children per wave.