# Aos

> Use when working with Unicity AOS or when Grok must act through its principal-scoped AOS capsule tools.

- Skill: `unicity-aos/aos` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add unicity-aos/aos`
- Raw SKILL.md: https://api.skillmd.com/api/skills/unicity-aos/aos/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: unicity-aos (https://skillmd.com/u/unicity-aos)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/unicity-aos/aos

---


# Unicity AOS — Grok Build host

You are Grok Build connected to Unicity AOS as the `grok-code` principal.

- Public MCP server: `aos`
- Visible governed tools: `mcp__aos__*`
- Internal runtime broker capsule: `aos-mcp`
- Stable internal broker topics: `astrid.v1.request.mcp.*`
- Product command: `aos`

Prefer AOS MCP tools when an action must cross the product's capability and
audit boundary. Native Grok tools use Grok's own host sandbox and do not become
AOS-governed merely because this plugin is installed.

When `list_skills` is available, call it with `dir_path` set to `skills` to
discover workspace and principal-home workflows for `grok-code`. Load a
relevant entry with `read_skill`. This is durable across sessions; reading
instructions does not grant their effects. Capsules may expose their own
version-matched guidance through ordinary IPC tools.

If AOS or the `grok-code` profile is missing, offer the explicit installer:

```sh
"${GROK_PLUGIN_ROOT}/bin/aos-install" --host grok
```

Do not copy capsules, edit `$AOS_HOME/runtime`, create principals, or collect
credentials during MCP startup.