agent-orchestrator: Skill for Codex

.agents/skills/ao-desktop-dev/SKILL.md

ao-desktop-dev is a skill for Codex from Untrivial-ai/agent-orchestrator. It costs 88 tokens per session (2,069 once invoked), scanned A, original, Apache-2.0.

A development workflow for running and inspecting the AO Electron desktop application from its current source code. Electron is a framework for building desktop apps with web technologies.

In plain words
What is it for?
Use it to launch, restart, troubleshoot, or visually check the AO desktop app, review changes from multiple branches, and investigate renderer, preload, daemon, or data-mode problems.
Why use it?
It helps distinguish the current build and data source from stale app processes, conflicting ports, or mismatched background services. It also provides separate handling for test data and the machine’s real AO data.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is Untrivial-ai/agent-orchestrator's own configuration. It tells Codex how to work on agent-orchestrator itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agent-orchestrator configures →

About the project

Agent Orchestrator is a local desktop workspace for running and supervising multiple coding agents, giving each task its own session, workspace, branch, and feedback loop. It is for developers coordinating agent fleets across repositories, pull requests, CI runs, reviews, and merges. The catalogue entries are commands, skills, and instructions for working with this orchestrator.

Untrivial-ai/agent-orchestrator · 13,596 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to Untrivial-ai/agent-orchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Untrivial-ai/agent-orchestrator/main/.agents/skills/ao-desktop-dev/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Untrivial-ai/agent-orchestrator

Made for: Codex.

Wrote 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.

agentmods badge for ao-desktop-dev

README.md
[![agentmods](https://agentmods.dev/badge/skills/untrivial-ai/agent-orchestrator/ao-desktop-dev/github.svg)](https://agentmods.dev/skills/untrivial-ai/agent-orchestrator/ao-desktop-dev)
Your own site
<a href="https://agentmods.dev/skills/untrivial-ai/agent-orchestrator/ao-desktop-dev"><img src="https://agentmods.dev/badge/skills/untrivial-ai/agent-orchestrator/ao-desktop-dev/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ao-desktop-dev

Your own site · 80×15
<a href="https://agentmods.dev/skills/untrivial-ai/agent-orchestrator/ao-desktop-dev"><img src="https://agentmods.dev/badge/skills/untrivial-ai/agent-orchestrator/ao-desktop-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,069 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 110
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00088 $0.02069
Opus 5.5 $0.00035 $0.00828
Sonnet 5.5 $0.00018 $0.00414
Haiku 4.5 $0.00009 $0.00207

Measured 1mo ago against content hash a5925b502599, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ao-desktop-dev 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 1mo ago.

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.

.agents/skills/ao-desktop-dev/SKILL.md · 159 lines

How it starts

The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AO Desktop Dev

Run the Electron application from the current checkout and verify it in the native window. Keep the dev daemon, renderer, Electron preload, and selected data mode explicit so the user never reviews a mock or stale build by accident.

Choose the data mode

Ask only when the request does not make the desired data source clear.

  • Use isolated mode by default for implementation and destructive testing. Electron uses port 3002, ~/.ao/dev/running.json, ~/.ao/dev/data, and ~/.ao/dev/electron.
  • Use real-data mode only when the user explicitly asks to see this machine's actual AO projects or sessions. Start the checkout's dev daemon on the isolated dev port/run file while pointing AO_DATA_DIR at the real AO data directory. This is a separate daemon process using real data; do not describe it as the installed app's daemon.
  • Never try to attach an unpackaged Electron app directly to a packaged daemon from another checkout. The supervisor intentionally rejects daemon identity mismatches.
  • Warn before actions in real-data mode that create, terminate, rename, or otherwise mutate sessions. Merely opening and inspecting the UI is expected.
  • Real-data mode reads the same database as the installed app, so both windows show the same projects and sessions. Quit the packaged app first where possible: two daemons sharing one SQLite database can cross-talk, and acting on the wrong window runs unmerged code against real sessions. The dev window is marked with an Agent Orchestrator (dev) title, the default Electron dock icon, and an in-app dev badge — verify those markers before acting.

Preflight

  1. Work from the repository root and inspect git status --short --branch.
  2. Read frontend/package.json, frontend/src/main.ts, and frontend/forge.config.ts when the launch behavior may have changed. Treat source as authoritative over this skill.
  3. Confirm Node/npm and the Go version required by backend/go.mod are available. Run npm ci in frontend/ only when dependencies are absent or inconsistent; do not reinstall on every launch.
  4. Check for an existing dev instance from this exact checkout before starting another. Do not kill by process name alone, and never terminate every Electron process.

Read the full file on GitHub · 159 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 1mo ago Changed · +1 lines a5925b502599
  2. 1mo ago Changed · +14 lines 56ee60242af9
  3. 1mo ago First seen · 144 lines · 88 tokens per session scan A a549d9f6362b

Subscribe to this mod's changes

ao-desktop-dev is a skill published in the GitHub repository Untrivial-ai/agent-orchestrator (13,596 stars, last pushed 2d ago), licensed Apache-2.0. It adds 88 tokens to every session and 2,069 once invoked, about $0.0004 per session on Opus 5.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-08-30.