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 codecast-sh/codecast --skill orchestrategit clone --depth 1 https://github.com/codecast-sh/codecastWrote 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/codecast-sh/codecast/orchestrate)<a href="https://agentmods.dev/skills/codecast-sh/codecast/orchestrate"><img src="https://agentmods.dev/badge/skills/codecast-sh/codecast/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/codecast-sh/codecast/orchestrate"><img src="https://agentmods.dev/badge/skills/codecast-sh/codecast/orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.01482 |
| Opus 5.5 | $0.00022 | $0.00593 |
| Sonnet 5.5 | $0.00011 | $0.00296 |
| Haiku 4.5 | $0.00006 | $0.00148 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are now acting as a conductor — your job is to drive a plan to completion by coordinating worker agents, not by writing code yourself.
Core loop
1. Read plan state
2. Identify ready tasks (unblocked, unclaimed)
3. Group into a wave of independent work
4. Spawn implementer agents (max 3-5 parallel, worktree-isolated)
5. When workers complete, spawn reviewers for their output
6. Handle review verdicts (pass → merge, needs_changes → re-implement, reject → escalate)
7. If all tasks done → run integration verification + critic sweep
8. If tasks remain → goto 2
Before you start
Read the plan and ground yourself:
cast plan context <plan_id> # or --current if already bound
If there's no plan doc yet, create one to serve as shared knowledge for all agents:
cast doc create "<Plan Title> — Shared Context" -t plan -c "Goal: ...
Constraints: ...
Decisions: (none yet)"
Decomposing (if tasks don't exist yet)
If the plan has no tasks, decompose it yourself:
- Read the plan goal and acceptance criteria
- Explore the codebase — use Glob, Grep, Read to understand the relevant code
- Write the steps in waves, one per line with what done means after
::. Steps in a wave run in parallel; a blank line starts a wave that needs every step of the one before:
cast plan steps <plan_id> - <<'STEPS'
Add status field to tasks schema :: <acceptance criteria and owned files>
Update task API to filter by status :: <...>
Backfill status on existing tasks :: <...>
Show the status filter on the board :: <...>
STEPS
Order by what a step needs, never by what comes first. A step that needs
only part of a wave goes in that same wave and gets its edge with cast task dep <step> --blocked-by <what it needs>.
Rules for decomposition:
- Schema/data model first, then backend logic, then UI, then polish
- Each task should produce a testable, committable change
- Include test-writing as part of feature tasks, not separate tasks
- Name tasks with specific files/functions, not generic descriptions
- Reference actual code paths you found during exploration
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 · +11 lines 3fabcbdf91a4
- 1mo ago First seen · 164 lines · 56 tokens per session scan A 2ed98decaba8
orchestrate is a skill published in the GitHub repository codecast-sh/codecast (40 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 1,482 once invoked, about $0.0002 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-30.
Other skills, from other repositories
google-agents-cli-scaffold
This skill should be used when the user wants to "create an agent project", "start a new ADK project", "build me a new agent", "add CI/CD to my project", "add deployment", "enhance my project", or "upgrade my project". Part of the agents-cli skills suite. Covers agents-cli scaffold create, scaffold enhance, and…
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
grocery-prices
A skill to calculate grocery prices with country-specific taxes.
honey-px
Read huge read-only text as PNG pages; big input cut.
honey-memory
Per-project persistent memory files indexed in MEMORY.md.
debate
Weigh one risky change against a named alternative through an advocate, a skeptic, and a neutral investigator, then recommend.