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 Rootly-AI-Labs/rootly-claude-plugin --skill announcegit clone --depth 1 https://github.com/Rootly-AI-Labs/rootly-claude-pluginWrote 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/rootly-ai-labs/rootly-claude-plugin/announce)<a href="https://agentmods.dev/skills/rootly-ai-labs/rootly-claude-plugin/announce"><img src="https://agentmods.dev/badge/skills/rootly-ai-labs/rootly-claude-plugin/announce.svg" alt="Measured on agentmods" 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.00046 | $0.01017 |
| Opus 5 | $0.00023 | $0.00508 |
| Sonnet 5 | $0.00009 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
announce 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 8d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Announcement
You are helping the user (often the incident commander) post a stakeholder-facing update on an incident. Write action — explicit confirmation required.
Workflow
1. Resolve the incident
$ARGUMENTS should contain an incident reference (UUID, INC-XXXX, or sequential number).
- If empty: call
mcp__rootly__listIncidentswithfilter_status="started",page_size=10, andsort="-started_at"and ask the user which incident to announce. - Otherwise call
mcp__rootly__getIncidentwith the incident reference exactly as provided. The MCP server accepts UUIDs plus sequential forms like4460,#4460, andINC-4460.
Once resolved, use the returned incident record for the full context.
2. Identify the publication target
Inspect the incident record for:
- An attached status page (often
status_page_idor similar field) - Public-facing flag (
is_public/private)
If the incident has a status page attached:
- Call
mcp__rootly__getStatusPagefor the page details (name, URL). - Call
mcp__rootly__listStatusPageTemplatesto surface preset update templates.
If no status page is attached, fall back to posting an incident event that surfaces in Rootly's internal stream — call mcp__rootly__createIncidentEvent instead. Make the distinction clear to the user.
3. Draft the update
Compose a 2–4 sentence update with this structure:
[Status verb: "Investigating" / "Identified" / "Monitoring" / "Resolved"] — [one-sentence summary of customer impact].
[Optional: what we know about the cause, briefly.]
[Optional: what we're doing about it.]
[Next update: in [duration] / when status changes.]
Keep it stakeholder-grade: no Rootly internal IDs, no engineer names, no jargon.
4. Show the draft
**Incident**: [INC-XXXX] [title] — [severity], [status]
**Posting to**: [Status page name + URL] | [Internal incident stream if no status page]
**Visibility**: [Public / Internal]
**Draft update:**
> [the drafted message]
Confirm to post this update? (yes / edit / no)
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.
- 8d ago First seen · 105 lines · 46 tokens per session scan A 51c8467f1020
announce is a skill published in the GitHub repository Rootly-AI-Labs/rootly-claude-plugin (1 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,017 once invoked, about $0.0002 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-30.
Other skills, from other repositories
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.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.