Skip to content
Back to skills

Agi Super Team Sync

ASecurity

Preview, install, or update AGI Super Team in Codex. Use when the user asks to inject the Musk CEO into the global main agent, list or install a C-suite team, or sync bundled specialist agents.

  • 92 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 22, 2026
ai-agentspythonbashdatabase

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 22, 2026

npx -y skills add aAAaqwq/AGI-Super-Team --skill agi-super-team-sync --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agi Super Team Sync?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agi Super Team Sync
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aaaaqwq-agi-super-team-sync-agi-super-team/badge)](https://www.skillsdirectory.com/skills/aaaaqwq-agi-super-team-sync-agi-super-team)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agi-super-team-sync
description: Preview, install, or update AGI Super Team in Codex. Use when the user asks to inject the Musk CEO into the global main agent, list or install a C-suite team, or sync bundled specialist agents.
---

# 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:

   ```bash
   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:

   ```bash
   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:

```bash
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:

```toml
[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.

Files in this skill

  • SKILL.md3.6 KB
  • agents/openai.yaml227 B
  • scripts/install_codex_team.py11.2 KB
  • scripts/sync_codex_agents.py11.5 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.