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 prefect-cross-flow-to-orchestragit 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/prefect-cross-flow-to-orchestra)<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/prefect-cross-flow-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/prefect-cross-flow-to-orchestra/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/prefect-cross-flow-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/prefect-cross-flow-to-orchestra.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.00072 | $0.01528 |
| Opus 5 | $0.00036 | $0.00764 |
| Sonnet 5 | $0.00014 | $0.00306 |
| Haiku 4.5 | $0.00007 | $0.00153 |
Grade A, and why
prefect-cross-flow-to-orchestra 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Prefect cross-flow coordination uses two patterns: run_deployment() (trigger a separate deployment, optionally waiting for completion) and subflows (calling one @flow from inside another). In Orchestra, both patterns become separate pipelines. The recommended approach for cross-pipeline triggering is trigger_events: on the downstream pipeline, which fires when an upstream pipeline reaches a given status.
Important schema note: TRIGGER_PIPELINE does not appear in the verified IntegrationJobsEnum. For cross-pipeline triggering, use trigger_events: on the downstream pipeline root. If your Orchestra version does support TRIGGER_PIPELINE as a task job, verify against your instance's schema before using it.
Parameter Mapping
| Prefect construct | Orchestra equivalent | Notes |
|---|---|---|
run_deployment("name/deployment") — fire and wait |
trigger_events: on downstream pipeline |
downstream waits for upstream SUCCEEDED |
run_deployment(..., timeout=0) — fire and forget |
trigger_events: on downstream pipeline |
set statuses: [SUCCEEDED] on upstream |
| Prefect Automation: on parent SUCCEEDED → run child | trigger_events: at child pipeline root |
|
child_flow() called inside parent_flow() (subflow) |
child → separate Orchestra pipeline; trigger_events: |
no inline subpipeline concept |
run_deployment(..., parameters={...}) |
trigger_events: [{..., run_inputs: {...}}] |
|
Sequential run_deployment calls |
chain via trigger_events: with pipeline_id of each upstream |
|
await run_deployment(...) (async) |
same as sync — trigger_events: |
Orchestra handles async natively |
Orchestra YAML Structure
# On the DOWNSTREAM (child) pipeline:
version: v1
name: downstream-pipeline
trigger_events:
- type: pipeline
pipeline_id: "uuid-of-upstream-pipeline" # UUID from Orchestra UI pipeline URL
run_inputs: # optional — equivalent to run_deployment parameters
env: prod
date: '{{ run_date }}'
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 · 155 lines · 72 tokens per session scan A 12992bf3280b
prefect-cross-flow-to-orchestra is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed 3d ago), licensed MIT. It adds 72 tokens to every session and 1,528 once invoked, about $0.0004 per session on Opus 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
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…
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…