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 setup-incident-slack-summarygit 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/setup-incident-slack-summary)<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/setup-incident-slack-summary"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/setup-incident-slack-summary/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/setup-incident-slack-summary"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/setup-incident-slack-summary.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.00099 | $0.01406 |
| Opus 5.5 | $0.00040 | $0.00562 |
| Sonnet 5.5 | $0.00020 | $0.00281 |
| Haiku 4.5 | $0.00010 | $0.00141 |
Grade A, and why
setup-incident-slack-summary 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 16d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up the scheduled incident Slack summary pipeline
You deploy one Orchestra pipeline into the user's workspace from the template in assets/pipeline.yml. It has two tasks:
- Run Agent — an Orchestra agent lists incidents with the pipeline's filter inputs, keeps those created inside the lookback window, and sets two outputs:
results(a one-line plain-text fallback) andblocks(Slack Block Kit JSON: a header plus a table with severity emoji, linked incident name, status, created and last updated). - Send Slack message — posts
blocks(withresultsas the notification text) to theslack_channelinput.
The pipeline's inputs (slack_channel, lookback_days, statuses, severities, name_contains) are what scheduled runs use by default, and anyone can override them on a manual run. So the defaults you set here are the user's standing filter.
Step 1 — Gather settings
Ask for anything the user hasn't given, in one message, offering the defaults:
| Setting | Default | Notes |
|---|---|---|
| Slack channel | none, must ask | e.g. #data-incidents |
| Schedule | Mondays 09:00 Europe/London | Convert to a 6-field AWS EventBridge cron (see below) |
| Lookback window | 7 days | Whole days |
| Statuses | OPEN,INVESTIGATING |
Valid: OPEN, INVESTIGATING, RESOLVED, DISMISSED. "Open" means OPEN,INVESTIGATING (anything not yet resolved or dismissed) |
| Severities | CRITICAL,HIGH,MEDIUM,LOW |
Any subset |
| Name filter | none | Substring match on incident name, e.g. dbt |
If the user said something like "just set it up", use the defaults and only ask for the channel.
Cron: Orchestra needs 6 fields (minute hour day-of-month month day-of-week year), and exactly one of day-of-month / day-of-week must be ?. Examples: weekly Monday 9am 0 9 ? * MON *; daily 8am 0 8 * * ? *; weekdays 9am 0 9 ? * MON-FRI *. A 5-field cron fails validation. Set __SCHEDULE_NAME__ to a readable label such as Mondays at 9am (Europe/London).
What ships with it
1 file 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.
- 16d ago First seen · 72 lines · 99 tokens per session scan A ca46e89ad949
setup-incident-slack-summary is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 1,406 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-10-09.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…