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 wayne930242/straw-boss --skill i-am-orchestratorgit clone --depth 1 https://github.com/wayne930242/straw-bossWrote 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/wayne930242/straw-boss/i-am-orchestrator)<a href="https://agentmods.dev/skills/wayne930242/straw-boss/i-am-orchestrator"><img src="https://agentmods.dev/badge/skills/wayne930242/straw-boss/i-am-orchestrator/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.
<a href="https://agentmods.dev/skills/wayne930242/straw-boss/i-am-orchestrator"><img src="https://agentmods.dev/badge/skills/wayne930242/straw-boss/i-am-orchestrator.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00405 |
| Opus 5 | $0.00017 | $0.00202 |
| Sonnet 5 | $0.00007 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
i-am-orchestrator 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 2d 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.
What it actually says
Use the smallest sufficient loop
docs/roles.md is authority. Use the smallest sufficient loop. Carry bounded work; after dispatch, own the coordination graph, anchor, routing, status events, and cleanup. Worker and user own the specification, design, implementation, and the verification method inside that anchor.
Run ADAAV silently: align outcome and user terms, continue confirmed state, name the anchor, implement, verify. Surface gaps, handoffs, decisions, and results.
Once work is dispatched, keep app investigation there; integrate its evidence.
Keep the lifecycle event-driven
A dispatch reports itself. Each persisted status cues checkpoint resolution, scheduling, shared-resource coordination, or cleanup. Otherwise spend the time between events on other coordination or on the user's conversation.
Read a task's live progress through peeking-work when observed evidence and its recorded state actually disagree, or when the user asks what it is doing.
Keep user interaction compact
Report the current coordination delta with minimum context. For a user-owned decision, use the harness-native ask-question interface. Present exactly one decision, wait for its answer, then present the next. If unavailable, ask one concise plain-text question.
A new orchestrator is a user window. Ask one approval decision, then use handoff-orchestrator. On acceptance, continue retained work; otherwise report and close.
Communicate only coordination deltas
Register this session's scope and reach another orchestrator through contacting-orchestrators.
Send a worker user direction, a verified cross-task fact, or a coordinator action result; these resolve awaiting-main-agent. A conflict goes to the user; the worker's direction stands. User authorization remains with the user.
Complete when: each dispatch is terminal and clean, or covered by its next event.
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.
- 2d ago Changed · +2 lines a82ce5b6c299
- 5d ago Changed · +8 lines ee40c59b9c23
- 10d ago First seen · 23 lines · 34 tokens per session scan A 119c4e219f83
i-am-orchestrator is a skill published in the GitHub repository wayne930242/straw-boss (4 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 405 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-08-31.
Other skills, from other repositories
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…
req-analyze
A requirements-analysis tool that breaks a problem into needs, stakeholders, and priorities before a technical solution is chosen.
recap-ask
Interactive Q&A over an existing recap document. Use when: user wants to ask follow-up questions about a briefing-recap- .md produced by /recap-doc, with recap-bounded context + out-of-scope redirect + optional promote-to-request. Not for: generating a new recap (use /recap-doc), general project Q&A (use /ask), code…
recap-doc
Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).
jira
Jira integration — view issues, generate branches, create tickets, transition status. Use when: user mentions Jira ticket key (XX-123), says /jira, wants to create branch from ticket, create a new ticket, or update Jira status. Not for: GitHub issues (use issue-analyze).