A first-time setup skill for the Rootly plugin. Rootly is an incident-management service, and the setup checks its connection and logged-in account before guiding configuration.

Use it after installing the Rootly plugin to verify the MCP connection, confirm the current Rootly user and team, and configure access.

It helps reveal whether the Rootly service is reachable and authentication is working. It also provides troubleshooting guidance when OAuth login or the connection fails.

setup — Skill for Claude Code and Codex by Rootly-AI-Labs: A first-time setup skill for the Rootly plugin.

Install

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.

agentmods

npx agentmods add skills/rootly-ai-labs/rootly-claude-plugin/setup

Any agent

npx skills add Rootly-AI-Labs/rootly-claude-plugin --skill setup

Clone the repo

git clone --depth 1 https://github.com/Rootly-AI-Labs/rootly-claude-plugin

Made for: Claude Code, Codex.

Or install rootly-claude-plugin, the plugin that ships this one along with the rest of its 18 skills, 3 agents, 2 hooks, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/rootly-ai-labs/rootly-claude-plugin/setup.svg)](https://agentmods.dev/skills/rootly-ai-labs/rootly-claude-plugin/setup)

Your own site

<a href="https://agentmods.dev/skills/rootly-ai-labs/rootly-claude-plugin/setup"><img src="https://agentmods.dev/badge/skills/rootly-ai-labs/rootly-claude-plugin/setup.svg" alt="Measured on agentmods" height="20"></a>

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 874 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00032	$0.00874
Opus 5	$0.00016	$0.00437
Sonnet 5	$0.00006	$0.00175
Haiku 4.5	$0.00003	$0.00087

Measured 4d ago against content hash 4bbbe15bc367, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup 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 4d 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.

skills/setup/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Rootly Plugin Setup

You are running the first-time setup for the Rootly Claude plugin. Follow these steps in order:

Step 1: Verify MCP Connection

First, test the MCP server connection by calling mcp__rootly__get_server_version.

Succeeds: The MCP server is reachable. Continue to Step 2.
Fails with 401 / OAuth prompt: Claude should automatically start the OAuth2 flow -- a browser window will open for you to log in to Rootly and grant access. Once authorized, retry mcp__rootly__get_server_version.
Fails with other error: MCP server connection issue. Check network connectivity to https://mcp.rootly.com.

Step 2: Verify Authentication

Call mcp__rootly__getCurrentUser to confirm your identity.

Succeeds: Authentication is working. Report the authenticated user and team, then continue to Step 3.
Fails: Authentication issue. Provide troubleshooting:

Authentication Troubleshooting

This plugin uses OAuth2 by default -- Claude handles the login flow automatically when it connects to the MCP server. No API token is needed for MCP commands.

If OAuth2 is not working:

Ensure your Rootly organization has OAuth2 enabled

Try disconnecting and reconnecting the MCP server: /mcp > find Rootly > disconnect > reconnect

Check that your browser can reach https://rootly.com/oauth/authorize

Fallback: API Token (for hook scripts or environments without browser access)

Hook scripts (active-incident warnings on commit/push) still need an API token:

Go to your Rootly dashboard: Settings > API Keys

Create a new API key

Provide the token through the plugin's userConfig prompt, or export ROOTLY_API_TOKEN="..."

API tokens are optional for MCP commands -- OAuth2 is the recommended auth method.

Then stop here -- no further steps possible without working authentication.

Step 3: Service Mapping Configuration

Check if .claude/rootly-config.json exists in the current project directory.

Read the full file on GitHub · 89 lines

Changes

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.

4d ago First seen · 89 lines · 32 tokens per session scan A 4bbbe15bc367

Subscribe to this mod's changes

setup 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 874 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.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens