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 slack-dagster-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/slack-dagster-to-orchestra)<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/slack-dagster-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/slack-dagster-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/slack-dagster-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/slack-dagster-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.00105 | $0.01725 |
| Opus 5 | $0.00053 | $0.00863 |
| Sonnet 5 | $0.00021 | $0.00345 |
| Haiku 4.5 | $0.00011 | $0.00172 |
Grade A, and why
slack-dagster-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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slack: Dagster -> Orchestra Conversion
Overview
Dagster Slack notifications come in two forms:
- Run-status sensors / hooks (
make_slack_on_run_failure_sensor,@failure_hook,@success_hook) — fire when a run or op changes status; not pipeline steps. - Explicit messages inside an op (
context.resources.slack.get_client().chat_postMessage(...)) — a message sent at a specific point in the run.
In Orchestra these map to:
alertsblock (pipeline-level or task-level) — fires on status change; no pipeline slot consumed.SLACKpipeline task (integration: SLACK,integration_job: SEND_SLACK_MESSAGE) — fires at a specific position, when content depends on runtime logic or ordering matters.
Decision Guide
| Dagster pattern | Orchestra equivalent |
|---|---|
make_slack_on_run_failure_sensor |
Pipeline-level alerts block (statuses: [FAILED]) |
@failure_hook / @success_hook on whole job |
Pipeline-level alerts block |
@failure_hook / @success_hook on a single op |
Task-level alerts block on that task |
SlackResource.chat_postMessage inside an op (mid-run) |
SLACK + SEND_SLACK_MESSAGE task |
| Slack message at end of job | Pipeline-level alerts block (statuses: [SUCCEEDED]) |
Option 1: Orchestra Alerts (YAML) — recommended for sensors & hooks
AlertModel schema
| Field | Required | Notes |
|---|---|---|
name |
yes | Unique within scope |
statuses |
yes | FAILED, SUCCEEDED, CANCELLED, WARNING, SKIPPED |
destinations |
yes | One entry per channel/target |
custom_message |
no | Appended to the standard Orchestra alert message |
AlertDestinationModel
| Field | Value / notes |
|---|---|
integration |
SLACK, EMAIL, PAGER_DUTY, WEBHOOK, MICROSOFT_TEAMS |
destination |
Channel name (e.g. #data-alerts) — required for Slack |
connection_id |
Required for PagerDuty, Teams, Webhook |
version: v1
name: my-pipeline
alerts:
- name: on-failure-slack
statuses:
- FAILED
destinations:
- integration: SLACK
destination: '#data-alerts'
custom_message: 'Check the logs and rerun from the failed task.'
pipeline:
stage-001:
tasks:
task-001:
# ... your tasks here
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 · 179 lines · 105 tokens per session scan A e490bb976795
slack-dagster-to-orchestra is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed 3d ago), licensed MIT. It adds 105 tokens to every session and 1,725 once invoked, about $0.0005 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…