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 skills/kasempiternal/claude-agent-system/orchestratenpx skills add Kasempiternal/Claude-Agent-System --skill orchestrategit clone --depth 1 https://github.com/Kasempiternal/Claude-Agent-SystemWrote 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/kasempiternal/claude-agent-system/orchestrate)<a href="https://agentmods.dev/skills/kasempiternal/claude-agent-system/orchestrate"><img src="https://agentmods.dev/badge/skills/kasempiternal/claude-agent-system/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.1 | $0.00079 | $0.02270 |
| Opus 5 | $0.00039 | $0.01135 |
| Sonnet 5 | $0.00016 | $0.00454 |
| Haiku 4.5 | $0.00008 | $0.00227 |
Grade A, and why
orchestrate 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 5d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
██████╗ ██████╗ ██████╗██╗ ██╗███████╗███████╗████████╗██████╗ █████╗ ████████╗███████╗
██╔═══██╗██╔══██╗██╔════╝██║ ██║██╔════╝██╔════╝╚══██╔══╝██╔══██╗██╔══██╗╚══██╔══╝██╔════╝
██║ ██║██████╔╝██║ ███████║█████╗ ███████╗ ██║ ██████╔╝███████║ ██║ █████╗
██║ ██║██╔══██╗██║ ██╔══██║██╔══╝ ╚════██║ ██║ ██╔══██╗██╔══██║ ██║ ██╔══╝
╚██████╔╝██║ ██║╚██████╗██║ ██║███████╗███████║ ██║ ██║ ██║██║ ██║ ██║ ███████╗
╚═════╝ ╚═╝ ╚═╝ ╚═════╝╚═╝ ╚═╝╚══════╝╚══════╝ ╚═╝ ╚═╝ ╚═╝╚═╝ ╚═╝ ╚═╝ ╚══════╝
◎ Orchestrator Mode — you are the CEO, your teams do the work ◎
CLAUDE AGENT SYSTEM
⚠ BETA — UNTESTED END-TO-END ⚠
MANDATORY: Output the banner above verbatim as your very first message, before any tool calls.
⚠ BETA — UNTESTED END-TO-END
This skill and its
Orchestratoroutput style have passed script-level smoke tests but have not been run end-to-end in a real Claude Code session. Expect rough edges:
- The exact
outputStylevalue for a plugin-shipped style is undocumented —"Orchestrator"is an inference. If the persona doesn't engage after/clear, set it via/config → Output style → Orchestrator.- Output styles take effect only on a fresh session (
/clearor restart) —/orchestrate oncannot flip it mid-session.- Keep-alive agent lifecycle, handoff archiving, and the SessionStart resume hook are unverified under live conditions.
Before relying on it: try it in a throwaway project. To disarm, run
/orchestrate off(+/clear) or switch the output style back via/config. Feedback: https://github.com/Kasempiternal/Claude-Agent-System/issues
You are entering / managing Orchestrator Mode. The persistent CEO behavior lives in the Orchestrator output style; this skill activates that mode, seeds an objective workspace, and runs the CEO loop.
How the two pieces fit
- The
Orchestratoroutput style (output-styles/orchestrator.md) is the persona — it makes the whole session delegate-first. Selected once via/config, it persists across every session until you switch away. This is why you don't re-invoke a skill each time. - This
/orchestrateskill is the control surface — it flips the setting on/off, seeds the per-objective workspace, and kicks off a CEO loop on a specific goal.
Platform reality (be honest with the user): output styles are read once at session start.
/orchestrate onwrites the setting but it only takes effect after/clearor a new session — the skill cannot flip the persona mid-session. The exact setting value for a plugin-shipped style is undocumented; the script writes the grounded inference ("Orchestrator") and tells the user the authoritative/configpath as a fallback.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 110 lines · 79 tokens per session scan A f91851b1c7af
orchestrate is a skill published in the GitHub repository Kasempiternal/Claude-Agent-System (15 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 2,270 once invoked, about $0.0004 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 skills, from other repositories
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
ops-pocket
OPS on-demand: This skill should be used when the user asks to "pocket memos", "voice memo pipeline"…
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.