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-statusgit 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-status)<a href="https://agentmods.dev/commands/iii-experimental/agentos/agentos-status"><img src="https://agentmods.dev/badge/commands/iii-experimental/agentos/agentos-status.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.00015 | $0.00048 |
| Opus 5 | $0.00008 | $0.00024 |
| Sonnet 5 | $0.00003 | $0.00010 |
| Haiku 4.5 | $0.00002 | $0.00005 |
Grade A, and why
agentos-status scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:3111/api/dashboard/stats | jq . What it actually says
Check AgentOS status:
curl -s http://localhost:3111/api/dashboard/stats | 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 · 15 tokens per session scan A f3a8a467f06f
agentos-status is a command published in the GitHub repository iii-experimental/agentos (162 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 48 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (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
cc-council
Comprehensive multi-agent council review with 6 protocols, 10 specialists, scoped scoring (per-scope thresholds and weights), state machine orchestration, auto-fix, and 50+ configuration flags.
release
Release the plugin — bump version across 4 files, then optionally commit, tag, push, and create a GitHub Release.
fierce-review
Deterministic adversarial code review (Workflow tier) for high-stakes scope.
micro-execute
Micro-task execution with per-task two-stage review (spec compliance + code quality).
design-review
Compare design (Figma URL or mockup image) against implementation to detect UI mismatches (colors, layout, typography).
help
Guide for using Team-Shinchan plugin.