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-alerts-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-alerts-to-orchestra)<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/prefect-alerts-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/prefect-alerts-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-alerts-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/prefect-alerts-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.00108 | $0.01882 |
| Opus 5 | $0.00054 | $0.00941 |
| Sonnet 5 | $0.00022 | $0.00376 |
| Haiku 4.5 | $0.00011 | $0.00188 |
Grade A, and why
prefect-alerts-to-orchestra scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
requests.post(PAGERDUTY_URL, json={"routing_key": PD_KEY, "event_action": "trigger"}) How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Prefect notifications live in three places: @flow(on_failure=...) / @flow(on_completion=...) hooks, @task(on_failure=...) hooks, and Prefect Automation notification actions. All three map to Orchestra's alerts: block, placed at pipeline level (for flow-level hooks) or task level (for task-level hooks). Orchestra supports six destination integrations: SLACK, EMAIL, PAGER_DUTY, MICROSOFT_TEAMS, WEBHOOK, and DATADOG.
Parameter Mapping
| Prefect construct | Orchestra field | Notes |
|---|---|---|
@flow(on_failure=[slack_hook]) |
statuses: [FAILED] + SLACK destination |
pipeline-level alerts: |
@flow(on_completion=[slack_hook]) |
statuses: [SUCCEEDED] + SLACK |
pipeline-level |
@flow(on_crashed=[hook]) |
statuses: [FAILED] |
no CRASHED status in Orchestra |
@flow(on_cancellation=[hook]) |
statuses: [CANCELLED] |
|
@task(on_failure=[hook]) |
task-level alerts: on that specific task |
|
| Prefect Automation → Slack notification | statuses: [FAILED/SUCCEEDED] + SLACK |
|
| Prefect Automation → email notification | statuses: [...] + EMAIL |
|
| Prefect Automation → PagerDuty action | statuses: [...] + PAGER_DUTY |
requires connection_id |
| Prefect Automation → Teams notification | statuses: [...] + MICROSOFT_TEAMS |
requires connection_id |
SlackWebhook.load("x").notify(...) |
SLACK destination with destination field |
channel from notify(channel=...) |
MicrosoftTeamsWebhook.load("x").notify(...) |
MICROSOFT_TEAMS with connection_id |
Valid statuses values: FAILED, SUCCEEDED, CANCELLED, WARNING, SKIPPED
Destination rules:
SLACKandEMAIL→ requiredestinationfield (channel or address)PAGER_DUTY,MICROSOFT_TEAMS,WEBHOOK,DATADOG→ requireconnection_id(Orchestra connection name with 5-digit suffix)
Orchestra YAML Structure
# Pipeline-level alerts
alerts:
- name: <unique-alert-name>
statuses:
- FAILED # FAILED | SUCCEEDED | CANCELLED | WARNING | SKIPPED
destinations:
- integration: SLACK # SLACK | EMAIL | PAGER_DUTY | MICROSOFT_TEAMS | WEBHOOK | DATADOG
destination: '#channel' # required for SLACK and EMAIL only
connection_id: null # required for PAGER_DUTY, MICROSOFT_TEAMS, WEBHOOK, DATADOG
custom_message: null # optional, max ~200 chars
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 · 181 lines · 108 tokens per session scan A 0f586c70dec5
prefect-alerts-to-orchestra is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed 3d ago), licensed MIT. It adds 108 tokens to every session and 1,882 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…