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 EternallLight/tgc-skills --skill orchestrate-plangit clone --depth 1 https://github.com/EternallLight/tgc-skillsWrote 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/eternalllight/tgc-skills/orchestrate-plan)<a href="https://agentmods.dev/skills/eternalllight/tgc-skills/orchestrate-plan"><img src="https://agentmods.dev/badge/skills/eternalllight/tgc-skills/orchestrate-plan/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/eternalllight/tgc-skills/orchestrate-plan"><img src="https://agentmods.dev/badge/skills/eternalllight/tgc-skills/orchestrate-plan.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.00155 | $0.05676 |
| Opus 5 | $0.00077 | $0.02838 |
| Sonnet 5 | $0.00031 | $0.01135 |
| Haiku 4.5 | $0.00015 | $0.00568 |
Grade B, and why
orchestrate-plan scanned grade B 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 11d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
remove that stall but let a worker run ANY command unattended — a malicious repo instruction or How it starts
The opening of the file, as written. The whole thing — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate Plan — execute a PLAN.md via fresh-context worker(s), one PHASE at a time
You are the orchestrator (manager). You do NOT write the implementation yourself.
You split a locked plan into context-window-sized phases and drive one or more worker
agents in separate cmux panes: feed each worker one phase at a time, /clear its context
before every phase, verify each phase, then move on — while keeping your own context clean
so you can run the whole plan without drowning in tool output.
When the plan touches independent repos (e.g. a backend api service + a web
frontend that both code to a contract the plan already fixes), run one worker pane per repo
in parallel and babysit them all with a single ~45s monitor loop.
Three non-negotiables:
- One phase per context window. A phase is a coherent slice of the plan sized to fit one worker context (it may be several commits). Split anything bigger; cluster anything trivially small.
- Fully clear the worker before each phase (
/clear, never/compact). Every phase starts pristine; the worker re-grounds from disk (PLAN.md + the brief +git log). Strictly more deterministic than carrying a lossy summary. - Keep the orchestrator's context clean. Never Read worker source files or full scrollback into your window. Verify with git plumbing + narrow greps. Summarize to the human; never paste screens.
Prerequisites: a locked plan file exists (written AND reviewed — not a vague idea; if there is
no plan, write one and get it approved first). You are inside a cmux workspace — this skill drives
cmux panes; the CLI cheat sheet lives in the cmux-orchestrate skill (its references/cmux-cli.md,
resolved relative to that skill's own directory). Verbatim templates are in this skill's
references/templates.md.
Worker engine — Claude Code (default) or Codex (optional)
The worker pane runs Claude Code (default) or OpenAI Codex. The user picks. Everything
about the orchestration (one phase per /clear, verify each phase, keep your context clean, GATE
irreversible phases, the === PHASE N DONE === marker, parallel lanes) is identical — only the
launch command and effort mechanics differ.
What ships with it
1 file 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.
- 11d ago First seen · 310 lines · 155 tokens per session scan B 695072795a12
orchestrate-plan is a skill published in the GitHub repository EternallLight/tgc-skills (8 stars, last pushed 1mo ago), licensed MIT. It adds 155 tokens to every session and 5,676 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…