Installation Guide
Install an AI Agent OS ROM into your workspace in a few steps.
Prerequisites
- A workspace directory for your AI agent
- Git (for fetching skills with
gitsource type) - An AI agent runtime (e.g., Claude Code, Codex, or any LLM-based agent)
Step 1: Choose a ROM
Browse the ROM catalog and pick the ROM that matches your use case:
| ROM | Best for |
|---|---|
| manager-heavy-core | Multi-agent teams, OKR-driven execution |
| trinity | AI employees with strict accountability |
| mentor-coordinator-core | Mentor-led coordination |
Step 2: Clone the ROM templates
# Clone the ROMs repository
git clone https://github.com/fractalmind-ai/agent-os-roms.git
cd agent-os-roms
# Choose your ROM (example: manager-heavy-core)
ROM=manager-heavy-coreStep 3: Copy OS core files
Copy the template files from the ROM into your workspace:
# Set your workspace path
WORKSPACE=~/my-agent-workspace
MANIFEST=roms/$ROM/manifest.yaml
# Copy all template files
cp -r roms/$ROM/templates/* $WORKSPACE/
# Create directories declared in install_boundary.creates_directories
sed -n '/^ *creates_directories:$/,/^ *[^ -]/{s/^ *- //p}' "$MANIFEST" \
| while IFS= read -r d; do mkdir -p "$WORKSPACE/$d"; done
# Create any missing files declared in install_boundary.creates_files
# (e.g. mentor-coordinator-core bundles 5 templates but declares 7 files)
sed -n '/^ *creates_files:$/,/^ *[^ -]/{s/^ *- //p}' "$MANIFEST" \
| while IFS= read -r f; do
[ -e "$WORKSPACE/$f" ] || { mkdir -p "$WORKSPACE/$(dirname "$f")"; touch "$WORKSPACE/$f"; }
doneThis copies the ROM's bundled template files, creates declared directories, then bootstraps any missing files as empty. The sed commands read only the scoped YAML block (creates_files or creates_directories), stopping at the next non-list key. Some ROMs (like manager-heavy-core) include all workspace files as templates; others (like mentor-coordinator-core) only include core templates — the loop handles both cases.
Step 4: Install required skills
Check the ROM's included_skills in manifest.yaml and install each one:
Git-sourced skills
# Create skills directory
mkdir -p $WORKSPACE/.agent/skills
# Example: install agent-manager skill
git clone https://github.com/fractalmind-ai/agent-manager-skill.git \
/tmp/agent-manager-skill
cp -r /tmp/agent-manager-skill/agent-manager \
$WORKSPACE/.agent/skills/agent-managerEmbedded skills
Embedded skills are already included in the ROM's templates/ directory. They are copied automatically in Step 3.
Step 5: Install optional skills (recommended)
Check optional_skills in the manifest and install any that you need:
# Example: install agent-calendar
git clone --branch v0.1.0 \
https://github.com/fractalmind-ai/agent-calendar-skill.git \
/tmp/agent-calendar-skill
cp -r /tmp/agent-calendar-skill/agent-calendar \
$WORKSPACE/.agent/skills/agent-calendarStep 6: Customize
Edit the following files to match your environment:
USER.md— Add your name, preferences, and collaboration notesTOOLS.md— Document local tools, SSH details, API keys (paths only, not secrets)HEARTBEAT.md— Configure your execution surface and heartbeat checks
Step 7: Bootstrap your agent
Point your AI agent to the workspace and let it read AGENTS.md on first run. The agent will:
- Read
SOUL.mdto understand its operating principles - Read
USER.mdto understand who it's helping - Initialize the memory system
- Start the heartbeat loop
Verification
After installation, verify that:
- [ ] All files listed in
install_boundary.creates_filesexist - [ ]
memory/andokrs/directories are writable - [ ] Each skill in
included_skillshas aSKILL.mdin.agent/skills/<name>/ - [ ] Your agent can read and follow
AGENTS.md
Skill Directory Structure
Each installed skill follows this structure:
.agent/skills/<skill-name>/
├── SKILL.md # Entry point — read this to use the skill
├── scripts/ # Executable scripts
├── references/ # Reference documentation
└── rules/ # Optional runtime rulesWhat's Next
- Configure your agent's heartbeat schedule
- Set up your first OKR in
OKR.md - Add tasks to
TODO.mdfor immediate work - Explore the Skills catalog for additional capabilities
Troubleshooting
Skill not found after install? Verify the skill directory exists at .agent/skills/<name>/SKILL.md. Check that the source.path in the manifest matches the directory structure in the git repo.
Agent doesn't follow OS rules? Ensure AGENTS.md is in the workspace root and your agent is configured to read it on session start.
Missing template files? Re-copy from roms/<rom-name>/templates/. Check the manifest's install_boundary.creates_files for the complete list.