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 cyanheads/courtlistener-mcp-server --skill orchestrationsgit clone --depth 1 https://github.com/cyanheads/courtlistener-mcp-serverWrote 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/cyanheads/courtlistener-mcp-server/orchestrations)<a href="https://agentmods.dev/skills/cyanheads/courtlistener-mcp-server/orchestrations"><img src="https://agentmods.dev/badge/skills/cyanheads/courtlistener-mcp-server/orchestrations/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/cyanheads/courtlistener-mcp-server/orchestrations"><img src="https://agentmods.dev/badge/skills/cyanheads/courtlistener-mcp-server/orchestrations.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.00159 | $0.05125 |
| Opus 5 | $0.00079 | $0.02563 |
| Sonnet 5 | $0.00032 | $0.01025 |
| Haiku 4.5 | $0.00016 | $0.00513 |
Grade A, and why
orchestrations 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 12d 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.
This is a copy
100% identical to orchestrations — 23 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Multi-phase work that chains several foundational skills against one or more MCP server projects. Typical triggers:
- "Build N new servers" / "scaffold and ship X, Y, Z" →
workflows/greenfield-build.md - "Update and release these servers" / "run maintenance and ship" →
workflows/maintenance-release.md - "QA / field-test / find-and-fix bugs in these servers" →
workflows/field-test-fix.md - "Fix these issues and ship" / handoff document with findings to act on →
workflows/fix-wrapup-release.md
Single-skill work — running just maintenance, just git-wrapup, just release-and-publish — invokes the foundational skill directly. Use this orchestrations skill when at least two phases need to chain.
Mental Model — Three Tiers
| Tier | Layer | Examples | Who reads it |
|---|---|---|---|
| 1 | Foundational task skills | git-wrapup, release-and-publish, maintenance, field-test, setup, design-mcp-server, polish-docs-meta, code-simplifier, add-tool, add-resource, add-service, add-test, etc. |
Orchestrator AND sub-agents (by direct path reference) |
| 2 | Orchestration workflows | The four files under workflows/ |
Orchestrator only |
| 3 | Router | This SKILL.md |
Orchestrator only |
Workflows in Tier 2 sequence Tier 1 skills with gates and verification. They never duplicate Tier 1 content — they direct to it. A workflow file says "Phase N: agent reads and runs skills/git-wrapup/SKILL.md," not "here's how to wrap up a release."
The orchestrator is the agent driving the workflow — the one reading this SKILL.md. Sub-agents the orchestrator spawns receive prompts pointing at Tier 1 skills directly; they do not receive this skill or the workflow file. That boundary prevents recursive sub-agent spawning.
Pick a Workflow
Identify the workflow from user intent first, then sanity-check against project state if intent is ambiguous.
| User intent / state signal | Workflow |
|---|---|
New scaffold(s) from bunx @cyanheads/mcp-ts-core init, no implementation yet (echo definitions still present, no released changelog) |
workflows/greenfield-build.md |
Existing server(s), bun outdated shows updates, want to land them and ship |
workflows/maintenance-release.md |
| Existing server(s), want to find bugs via live testing and fix them, optionally ship | workflows/field-test-fix.md |
| Existing server(s) with known issues (GH issues, handoff document, observed gap), want to fix and ship | workflows/fix-wrapup-release.md |
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.
- 12d ago First seen · 228 lines · 159 tokens per session scan A b6a53442b543
orchestrations is a skill published in the GitHub repository cyanheads/courtlistener-mcp-server (2 stars, last pushed 18d ago), licensed Apache-2.0. It adds 159 tokens to every session and 5,125 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to orchestrations, differing in 23 lines, and is treated as a copy.
Other skills, from other repositories
courtlistener-citation-validator
Validates legal citations in documents using the CourtListener MCP to detect AI-generated hallucinations and citation errors. Use when user uploads a legal brief, motion, or document and asks to validate, check, audit, or verify case citations. Triggers on phrases like "validate citations", "check for hallucinated…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
omh-rust
This is a Hermes-native rust workflow skill.
omh-code-review
This is a Hermes-native code-review workflow skill.
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
manage-schemas
Creates, views, edits, deletes, and validates note schemas for the MCP Task Orchestrator in .taskorchestrator/config.yaml — the templates that define which notes agents must fill at each workflow phase. Also recommends schema designs from a library of workflow patterns (autonomous coding loops, spec-driven teams…