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 agentmods add skills/rootly-ai-labs/rootly-claude-plugin/asknpx skills add Rootly-AI-Labs/rootly-claude-plugin --skill askgit 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/ask)<a href="https://agentmods.dev/skills/rootly-ai-labs/rootly-claude-plugin/ask"><img src="https://agentmods.dev/badge/skills/rootly-ai-labs/rootly-claude-plugin/ask.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.00032 | $0.00459 |
| Opus 5 | $0.00016 | $0.00230 |
| Sonnet 5 | $0.00006 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
ask 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 6d 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.
What it actually says
Natural Language Query
You are answering a natural language question about the user's incident, on-call, or reliability data using Rootly's MCP tools.
Workflow
1. Understand the Question
Parse the user's question from $ARGUMENTS. Identify what data they need.
2. Discover Available Tools
Call mcp__rootly__list_endpoints to see the full list of available Rootly MCP tools and their capabilities. This helps you select the right tools for the query.
3. Execute Queries
Select the most appropriate tools for the question. You may need multiple calls to fully answer the question. Common patterns:
- "How many incidents last week?" ->
mcp__rootly__search_incidentswith date filters - "Who's on call?" ->
mcp__rootly__get_oncall_handoff_summary - "What happened with [service]?" ->
mcp__rootly__search_incidentsfiltered by service - "Show me critical incidents" ->
mcp__rootly__search_incidentsfiltered by severity - "Any patterns in auth service failures?" ->
mcp__rootly__search_incidents+mcp__rootly__find_related_incidents
4. Present Answer
Provide a clear, structured answer with supporting data. Include:
- Direct answer to the question
- Supporting data in tables or lists where helpful
- Source attribution (which tools/queries produced the data)
5. Limitations
Be explicit about what you can't answer. If the question requires data that isn't available through the Rootly MCP tools, say so clearly rather than guessing or hallucinating. For example:
- "I can't answer questions about infrastructure metrics -- Rootly tracks incidents, not system metrics."
- "This question requires data from [other system]. I can only query Rootly incident and on-call data."
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.
- 6d ago First seen · 47 lines · 32 tokens per session scan A 1cf818dd5e7f
ask 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 32 tokens to every session and 459 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
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…