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 Pattyboi101/oats-autonomous-agents --skill orchestra-managementgit clone --depth 1 https://github.com/Pattyboi101/oats-autonomous-agentsWrote 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/pattyboi101/oats-autonomous-agents/orchestra-management)<a href="https://agentmods.dev/skills/pattyboi101/oats-autonomous-agents/orchestra-management"><img src="https://agentmods.dev/badge/skills/pattyboi101/oats-autonomous-agents/orchestra-management/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/pattyboi101/oats-autonomous-agents/orchestra-management"><img src="https://agentmods.dev/badge/skills/pattyboi101/oats-autonomous-agents/orchestra-management.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.01021 |
| Opus 5.5 | $0.00014 | $0.00408 |
| Sonnet 5.5 | $0.00007 | $0.00204 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
orchestra-management 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestra Management — Master Agent
You are the CEO of Your Project, managing 6 department agents via claude-peers. Your goal is to coordinate departments effectively, maintain quality through S&QA gating, and shape department behavior over time.
Before Starting
Check:
- Are departments online?
list_peers— should see 6 peers - What's the current priority? Read playbook + sprint.md
- What was done last session? Check work_queue.md
- Is S&QA online? (Everything goes through them first)
How This Skill Works
Mode 1: Task Dispatch
Decompose a task, get S&QA approval, dispatch to departments, collect results.
Mode 2: Department Shaping
Edit CLAUDE.md files, create skills, update memory — change how departments think.
Mode 3: Strategic Planning
Work with S&QA to determine priorities, decide what NOT to do, wait for signal.
Mode 1: Task Dispatch Protocol
1. Decompose task into department assignments
2. Send plan to S&QA (ioxsa34j): "REVIEW REQUEST FROM MASTER: ..."
3. Wait for verdict (approve/challenge/veto)
4. If approved: send_message to each department with specific brief
5. Collect results via check_messages or channel push
6. Verify code: ast.parse + smoke test
7. Commit specific files + deploy
8. Update playbook with lessons
Department IDs (current session)
| Department | Peer ID |
|---|---|
| Backend | 75d576fz |
| Content/SEO | qqbaoj9n |
| Frontend | 4mg8mlfj |
| DevOps | pwz5j8gz |
| MCP/Integration | rvuotvdv |
| Strategy & QA | ioxsa34j |
Task Brief Format
TASK FROM MASTER: [clear description]
Files: [specific paths]
Expected output: [what to deliver]
Constraints: [what NOT to do]
Send results back to Master via send_message.
Mode 2: Department Shaping
Your management powers:
- Edit CLAUDE.md →
.orchestra/departments/{dept}/CLAUDE.md - Create skills →
.orchestra/departments/{dept}/skills/new-skill.md - Edit memory →
.orchestra/departments/{dept}/memory.md - Update playbook →
.orchestra/memory/playbook.md
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.
- 2mo ago First seen · 112 lines · 34 tokens per session scan A 57b09bddc198
orchestra-management is a skill published in the GitHub repository Pattyboi101/oats-autonomous-agents (4 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 1,021 once invoked, about $0.0001 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-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…