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 orchestra-hq/orchestra-skills --skill create-orchestra-pipelinegit clone --depth 1 https://github.com/orchestra-hq/orchestra-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/orchestra-hq/orchestra-skills/create-orchestra-pipeline)<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/create-orchestra-pipeline"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/create-orchestra-pipeline/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/orchestra-hq/orchestra-skills/create-orchestra-pipeline"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/create-orchestra-pipeline.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.00108 | $0.01512 |
| Opus 5.5 | $0.00043 | $0.00605 |
| Sonnet 5.5 | $0.00022 | $0.00302 |
| Haiku 4.5 | $0.00011 | $0.00151 |
Grade A, and why
create-orchestra-pipeline 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 3d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Orchestra Pipeline
Author or update an Orchestra version: v1 pipeline definition — YAML or
OML — validate it, and fix
validation errors.
References
../../references/orchestra/pipeline/yaml-authoring.md— schema, integrations, variables, optional sections../../references/orchestra/pipeline/examples.md— multi-stage patterns (warehouse → LLM → messaging, agents)../../references/orchestra/mcp/tools-quick-ref.md—validate_pipeline,create_pipeline,update_pipeline- Orchestra docs for integration parameters not covered in the reference
Workflow
Step 1 — Understand the request
From the user message, determine:
- Purpose, integrations, and data flow
- Target file path (default:
orchestra/<descriptive-name>.ymlin the current repo); write.omlinstead when the user asks for OML or the repo already uses it - Connections, schedules, inputs, alerts, matrix, or anomaly detection requirements
If no filename is given, derive a short kebab-case name from the pipeline purpose.
When editing an existing pipeline, read the deployed one before changing it —
pipeline_context(<alias>) returns its full definition alongside its metadata, so there
is no guessing at the YAML structure it already uses. Check whether it's Git-backed or
Orchestra-backed before deciding how to apply the change; that metadata includes
storageProvider. For Git-backed pipelines, edit the repo YAML directly (the repo is
the source of truth, so read the deployed definition for context only); update_pipeline
cannot write to them. For Orchestra-backed pipelines with no local YAML, use the MCP
tools instead of authoring a file.
Step 2 — Match repo conventions
List existing pipeline definitions (typically orchestra/, or paths the user names). Read one or two
pipelines that use similar integrations before writing — match task group and task ID style,
connection references, and schedule format.
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.
- 3d ago Changed · +5 lines 11c9065e10c1
- 12d ago Changed ab8638f182aa
- 25d ago Changed · +13 lines · +22 tokens per session d7636f6148a1
- 1mo ago Changed · +3 lines ce8706819848
- 1mo ago Changed · +3 lines ed5738047894
- 1mo ago First seen · 106 lines · 86 tokens per session scan A 8144b84de5ca
create-orchestra-pipeline is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed yesterday), licensed MIT. It adds 108 tokens to every session and 1,512 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-09-09.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…