Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add choiyounggi/loop-orchestrator/plugin install loop-orchestratorWrote 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/choiyounggi/loop-orchestrator/orchestrate)<a href="https://agentmods.dev/skills/choiyounggi/loop-orchestrator/orchestrate"><img src="https://agentmods.dev/badge/skills/choiyounggi/loop-orchestrator/orchestrate/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/choiyounggi/loop-orchestrator/orchestrate"><img src="https://agentmods.dev/badge/skills/choiyounggi/loop-orchestrator/orchestrate.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.00089 | $0.02614 |
| Opus 5.5 | $0.00036 | $0.01046 |
| Sonnet 5.5 | $0.00018 | $0.00523 |
| Haiku 4.5 | $0.00009 | $0.00261 |
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 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
orchestrate — multi-session orchestrator
You are the orchestrator. You do not implement — sessions do. You clarify, decompose, distribute, review, integrate, and merge. Autonomy lives inside the implementation loop; two human gates bracket it (task-split, pre-merge).
Scripts referenced below live in ${CLAUDE_PLUGIN_ROOT}/skills/orchestrate/scripts/.
Communication: session→orchestrator via .orchestration/status/<task>.json;
orchestrator→session via tmux send-keys one-liners (templates/session-prompt.md).
Tool profile
Resolve the pluggable tool profile once up front:
sh ${CLAUDE_PLUGIN_ROOT}/scripts/resolve-tools.sh --summary. It maps capability
roles — intake (issue-tracker work-list source), knowledge (domain/policy),
tacit (incidents/danger zones), plan (planning skill), verify (test/build/QA
command), explore (code search), design (visual/UI spec, e.g. Figma) — to
whatever tools this installation has, or to generic defaults when unset (optional,
layered per-user then per-repo; see references/tool-profile.md). Use
knowledge/tacit yourself during Clarify/Decompose, and write each task's
resolved roles into its <tools_guidance> brief so worker sessions inherit them
even if they can't re-read the config. A role is a tool injected into one step,
never a loop: do not map a role to an implement/verify-loop tool or another
orchestrator (that nests loops); there is no implement role.
Preflight
Run ${CLAUDE_PLUGIN_ROOT}/hooks/preflight.sh to resolve git/tmux/jq paths and
surface any missing CLI. git, tmux, and jq are all required — if any is
missing, stop and ask the user to install it (the SessionStart preflight hook is
advisory only; this skill must hard-require them). For a missing tmux: with the
user's consent, install it (macOS: brew install tmux; otherwise advise) before
launching sessions. Never auto-install without consent.
Phase 0 — Intake + Clarify
Two ways the work-list arrives:
intakerole configured (e.g. an issue tracker) → if the user names a parent issue (key/URL), use the intake tool to read it and its children: the parent gives the overall goal/architecture, each child becomes a candidate task. Extract the issue key from a URL (last path segment). This is the "Jira-style" entry — only taken whenintakeis set and the user supplies an issue; otherwise:intakeunset, or a free-text goal → the natural-language path (default): decompose the goal yourself in Phase 2.
What ships with it
7 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.
- 2mo ago First seen · 165 lines · 89 tokens per session scan A ebc26c842780
orchestrate is a skill published in the GitHub repository choiyounggi/loop-orchestrator (2 stars, last pushed 3mo ago), licensed MIT. It adds 89 tokens to every session and 2,614 once invoked, about $0.0004 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
deploy-from-stale-worktree-silent-rollback
Diagnose "I deployed a new Cloud Run / Docker image but a bunch of recently merged fixes regressed in production." Use when: (1) the deploy script does gcloud builds submit ... "${SCRIPTDIR}" or docker build (build context = local filesystem, NOT a git ref), (2) the user has many git worktrees / multiple checkouts of…
docs-branch-off-feature-branch-smuggles-code
Catch the bug class where a "docs follow-up" PR silently ships the parent feature's code under a docs(sN): title because the docs branch was created from the current working branch (a feature branch), not from origin/main. Use when: (1) you just opened a PR titled docs(...) or chore(...) after wrapping up a feature…
merged-pr-not-deployed-gate-label-missing
Diagnose "I merged my PR + CI is green but the live service still doesn't show my changes." Use when: (1) a code-bearing PR has been squash-merged into main with all required status checks passing, (2) the user reports the change is still missing from the deployed environment minutes-to-hours later, (3) the repo has a…
multi-agent-skill-silent-phase-compression
Diagnose and fix silent compression of MANDATORY phases in multi-agent orchestrator skills (review panels, debate workflows, multi-reviewer pipelines). Use when: (1) a skill spec lists 10+ phases including parallel reviewer dispatch but the actual run "compresses Phase 4 (reflection) / Phase 5 (debate) / Phase 7…
pr-conflict-from-mid-flight-merges
A pull request that was clean when you opened it now says on GitHub "This branch has conflicts that must be resolved", because others landed on main over the days it sat open. Use when gh pr view N --json mergeable,mergeStateStatus returns CONFLICTING and DIRTY, when your branch carries commits you do not recognise…
pr-from-stale-branch-silently-reverts-newer-main-files
Trap: merging a PR whose branch carries an OLD TREE silently DELETES (reverts) files that landed on main after that tree was built — with NO merge conflict to warn you, because a deletion your own commit records is not a conflict. Use when: (1) about to gh pr create or squash-merge from a long-lived / earlier-branched…