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 mygit 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/my)<a href="https://agentmods.dev/skills/rootly-ai-labs/rootly-claude-plugin/my"><img src="https://agentmods.dev/badge/skills/rootly-ai-labs/rootly-claude-plugin/my.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.00043 | $0.00914 |
| Opus 5 | $0.00022 | $0.00457 |
| Sonnet 5 | $0.00009 | $0.00183 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
my 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your Rootly Dashboard
You are building a personal status board for the current Rootly user. Read-only, focused, and quick to scan.
Workflow
1. Identify the user
Call mcp__rootly__getCurrentUser. Capture:
user_id(UUID) — for filtering downstream callsnameandemail— for the header- Team membership if present in the response
If getCurrentUser fails, stop with a clear auth error message.
2. Pull the three data slices in parallel
You may issue these tool calls in parallel where the model supports it. Keep each call narrow — we want a fast dashboard, not a full audit.
a. Open action items
- Call
mcp__rootly__listAllIncidentActionItems(first page, page_size = 50). - Filter to items where
assigned_to_user_id(or equivalent field) matches the user, with status not indone/closed/cancelled.
b. Active incidents you're on
- Call
mcp__rootly__listIncidentswithfilter_status=startedandfilter_user_id=<user_id>if supported, or with the user's team viafilter_team_idsif individual filtering isn't available. - Page size 25 is plenty.
c. Upcoming shifts
- Call
mcp__rootly__listShiftsfor the current user, scoped to the next 7 days. - If individual user filtering isn't available, fall back to
mcp__rootly__list_shiftsand filter client-side.
3. Render the dashboard
## [User name]'s Rootly Dashboard
*[email] — [primary team if known]*
### Active Incidents ([N])
[For each: severity badge, INC-XXXX, title, your role, started X ago]
- 🔴 [INC-XXXX] [title] — your role: [responder/IC/observer], started [duration] ago
- 🟡 [INC-YYYY] [title] — your role: [responder], started [duration] ago
[If zero: "No active incidents you're responding to."]
### Open Action Items ([N])
[Cluster by incident, max 10 items]
#### [INC-XXXX] [title]
- [ ] [description] — due [date or "no due date"]
- [ ] [description]
[If zero: "No open action items assigned to you."]
### Upcoming On-Call ([N] shifts in the next 7 days)
- [Schedule name]: [start] → [end] ([role/level if available])
- [Schedule name]: [start] → [end]
[If currently on call:]
**Currently on call**: [Schedule name] until [end time].
[If zero: "No on-call shifts in the next 7 days."]
---
### Quick links
- `/rootly:status` — service health overview
- `/rootly:oncall` — full team on-call schedule
- `/rootly:action add <incident> "<desc>"` — capture a follow-up
- `/rootly:swap` — request a shift swap
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 · 90 lines · 43 tokens per session scan A 4674d3cf5e24
my 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 43 tokens to every session and 914 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.