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 agentmods add commands/sipyourdrink-ltd/bernstein/statusgit clone --depth 1 https://github.com/sipyourdrink-ltd/bernsteinWhat 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 | $0.00006 | $0.00037 |
| Opus 5 | $0.00003 | $0.00018 |
| Sonnet 5 | $0.00001 | $0.00007 |
| Haiku 4.5 | $0.00001 | $0.00004 |
Grade A, and why
status 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 yesterday.
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.
What it actually says
Show the current state of a Bernstein orchestration run: open tasks, running agents, completed work, cost, and error rates.
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.
- yesterday First seen · 6 lines · 6 tokens per session scan A 3cbcff637178
status is a command published in the GitHub repository sipyourdrink-ltd/bernstein (1,038 stars, last pushed today), licensed Apache-2.0. It adds 6 tokens to every session and 37 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
browser
Inspect and control the current AO session's target-isolated browser. The desktop app must be open. The agent and user share the same live page, cookies, navigation state, and WebContentsView; the runtime remains usable while the Browser panel is hidden. Tabs in this worker share an ephemeral browser profile, while…
preview
Open a URL or workspace file in the desktop browser panel for the current session, or start a deterministic session-owned dev server from an existing .ao/launch.json.
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
session
Manage agent sessions: list, inspect, rename, kill, restore, clean up, and claim PRs.
spawn
Spawn a worker agent session in a registered project. The session runs the chosen agent in a fresh git worktree. Register the project first with ao project add.
import
Import reads the legacy Agent Orchestrator flat-file store (/.agent-orchestrator) read-only and ports its projects and per-project settings into the rewrite database. Legacy files are never modified, and a re-run skips rows that already exist, so it is safe to run more than once. The daemon must be stopped before…