Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add SapienXai/AgentOS --skill agentos-codexgit clone --depth 1 https://github.com/SapienXai/AgentOSWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sapienxai/agentos/agentos-codex)<a href="https://agentmods.dev/skills/sapienxai/agentos/agentos-codex"><img src="https://agentmods.dev/badge/skills/sapienxai/agentos/agentos-codex.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00032 | $0.04736 |
| Opus 5 | $0.00016 | $0.02368 |
| Sonnet 5 | $0.00006 | $0.00947 |
| Haiku 4.5 | $0.00003 | $0.00474 |
Grade A, and why
agentos scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentOS Codex Skill
Use this skill for AgentOS changes. Keep it practical: inspect the current code first, use the existing OpenClaw boundary, and make the smallest change that improves real operator control.
Product North Star
AgentOS is the human operating layer above OpenClaw. OpenClaw remains the backend, orchestration, runtime, agent/session/task/model/device/integration layer.
AgentOS must not become a replacement orchestrator or an OpenClaw clone. It should expose, visualize, manage, and improve UX around OpenClaw-backed workspaces, agents, tasks, files, models, integrations, policies, approvals, cost visibility, and runtime state.
Success question: did this system take a real workload from the owner today?
Start Here
Before implementing, inspect the relevant local surfaces:
- Product and architecture:
README.md,docs/openclaw-sync-audit.md,docs/openclaw-gateway-first-migration.md - OpenClaw 2026.9.2 contract and certification:
docs/openclaw-2026.9.2-compatibility-audit.md - OpenClaw boundary:
lib/openclaw/client/,lib/openclaw/adapter/,lib/openclaw/application/,lib/openclaw/domains/ - AgentOS state/contracts:
lib/agentos/,hooks/use-mission-control-data.ts,hooks/use-task-feed.ts - UI:
components/mission-control/,components/operations/,app/*/page.tsx - API routes:
app/api/ - Release/install:
packages/agentos/package.json,packages/agentos/scripts/check-release-consistency.mjs,install.sh,install.ps1,.github/workflows/release-agentos.yml - Tests:
tests/, especially OpenClaw boundary, gateway-first, release consistency, and CLI smoke tests
OpenClaw-First Rules
- Check whether OpenClaw already provides the capability through Gateway RPC, SDK/config, CLI, session/task APIs, model APIs, integration APIs, or device APIs.
- Prefer native Gateway/API integration over CLI.
- Use CLI only when no stable native Gateway/API path exists, or for existing install, recovery, gateway process control, and unsupported Gateway operations.
- Any CLI fallback must be explicit, observable, and surfaced through diagnostics, logs, UI state, or returned metadata with reason and recovery path.
- Do not duplicate OpenClaw concepts unless AgentOS needs a UI projection, cache, adapter, or workspace-local sidecar.
- Keep AgentOS-specific state separate from OpenClaw runtime state.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today Changed 00c68db9976f
- 2d ago First seen · 365 lines · 32 tokens per session scan A 52b862cd0bd1
agentos is a skill published in the GitHub repository SapienXai/AgentOS (98 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 4,736 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent - run one issue/PR pipeline on one repository as a supervised fleet. Auto-pick items, preflight every candidate to one deterministic claim verdict, stand up one worker session per item in a dedicated folder, probe them each cycle with one script call…
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
feature-request
Conversational workflow for gathering user feedback and filing GitHub Issues on the Kiro Crew repository. Load when the user clicks "Request a Feature", wants to report a bug, or suggest an improvement.
goal-loop
Bootstrap a goal-driven self-improving AutoNudge loop from a goal plus an anchor directory, then run the board autonomously until the Definition of Done is met.
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, or (6) Perform any GitHub…
packet-factory
Creates, reviews, and dispatches atomic work packets. Every task with a side effect requires an APPROVED packet before execution. Scope is immutable after approval — expansion requires a new packet.