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/iii-experimental/agentos/agentos-orchestrategit clone --depth 1 https://github.com/iii-experimental/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/commands/iii-experimental/agentos/agentos-orchestrate)<a href="https://agentmods.dev/commands/iii-experimental/agentos/agentos-orchestrate"><img src="https://agentmods.dev/badge/commands/iii-experimental/agentos/agentos-orchestrate.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 | $0.00019 | $0.00078 |
| Opus 5 | $0.00010 | $0.00039 |
| Sonnet 5 | $0.00004 | $0.00016 |
| Haiku 4.5 | $0.00002 | $0.00008 |
Grade B, and why
agentos-orchestrate scanned grade B with 2 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 4d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -s -X POST http://localhost:3111/api/orchestrator/plan -H 'Content-Type: application/json' -d '{"description": "$ARGUMENTS"}' | jq . Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST http://localhost:3111/api/orchestrator/plan -H 'Content-Type: application/json' -d '{"description": "$ARGUMENTS"}' | jq . What it actually says
Orchestrate a feature:
curl -s -X POST http://localhost:3111/api/orchestrator/plan -H 'Content-Type: application/json' -d '{"description": "$ARGUMENTS"}' | jq .
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.
- 4d ago First seen · 10 lines · 19 tokens per session scan B 6ccb8013f2f2
agentos-orchestrate is a command published in the GitHub repository iii-experimental/agentos (162 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 78 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
agent
Create and manage custom AI agents.
deep-review
Multi-pass deep code review — security, quality, and test gaps.
analyze
Analyze Claude Code transcripts to surface subagent behavior and improvement opportunities.
release
Release the plugin — bump version across 4 files, then optionally commit, tag, push, and create a GitHub Release.
debate
Expert agents debate to find optimal solutions.
council-sweep
Walk the configured watch paths and run Council on every artifact modified in the last N hours (default 24h).