agentmods.dev

lookup

lookup is a skill for Claude Code from Rootly-AI-Labs/rootly-claude-plugin. It costs 45 tokens per session (1,173 once invoked), scanned A, original, Apache-2.0.

A skill for looking up services, teams, repositories, or catalogue entries in Rootly, an incident-management and service-ownership system.

In plain words
What is it for?
Use it during an outage or other service problem to find the responsible team, on-call details, service records, dependencies, and current incidents.
Why use it?
It helps identify who owns a failing service and shows related reliability information, dependencies, and active incidents.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the rootly-claude-plugin plugin — 17 skills, 3 agents, 2 hooks, 1 MCP server shipped together

not rated 1repo 3mo ago A scan 45 tokens original Apache-2.0

Good fit Use it during an outage or other service problem to find the responsible team, on-call details, service records, dependencies, and current incidents.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rootly-ai-labs/rootly-claude-plugin/lookup
View source ↗ Rootly-AI-Labs/rootly-claude-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.

Any agent
npx skills add Rootly-AI-Labs/rootly-claude-plugin --skill lookup
Clone the repo
git clone --depth 1 https://github.com/Rootly-AI-Labs/rootly-claude-plugin

Made for: Claude Code.

Or install rootly-claude-plugin, the plugin that ships this one along with the rest of its 17 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.

agentmods badge for lookup

README.md
[![agentmods](https://agentmods.dev/badge/skills/rootly-ai-labs/rootly-claude-plugin/lookup/github.svg)](https://agentmods.dev/skills/rootly-ai-labs/rootly-claude-plugin/lookup)
Your own site
<a href="https://agentmods.dev/skills/rootly-ai-labs/rootly-claude-plugin/lookup"><img src="https://agentmods.dev/badge/skills/rootly-ai-labs/rootly-claude-plugin/lookup/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.

agentmods 80×15 button for lookup

Your own site · 80×15
<a href="https://agentmods.dev/skills/rootly-ai-labs/rootly-claude-plugin/lookup"><img src="https://agentmods.dev/badge/skills/rootly-ai-labs/rootly-claude-plugin/lookup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,173 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.01173
Opus 5 $0.00023 $0.00587
Sonnet 5 $0.00009 $0.00235
Haiku 4.5 $0.00005 $0.00117

Measured 9d ago against content hash 88d4f004bc66, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

lookup 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 9d 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/lookup/SKILL.md · 132 lines

How it starts

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

Service / Team Lookup

You are answering "what is this thing and who owns it?" for a service, team, or catalog entity. The user may pass a partial or full name; do your best to resolve it.

Workflow

1. Resolve the target

$ARGUMENTS is the search term. It might be:

  • A service name (e.g. payments-api)
  • A team name (e.g. Platform)
  • A repository name
  • A catalog entity slug

Strategy:

  1. Try mcp__rootly__listServices with the term as a filter where supported. If the MCP tool offers a name/query filter, use it; otherwise fetch the first 50 and match client-side (case-insensitive substring).
  2. If no service match, try mcp__rootly__listTeams similarly.
  3. If still no match, try mcp__rootly__listCatalogEntities (across all catalogs).

Determine the kind of the resolved entity (service, team, or catalog-entity) — branch the rendering on that.

If multiple matches, list the top 5 and ask the user to disambiguate. Do not guess.

If no matches, say so and suggest the user check spelling or try a broader term.

2. Gather details — service path

If the resolved entity is a service:

  1. Call mcp__rootly__getService for the full record. Capture: name, description, owning team, environment, slug, URL.
  2. Call mcp__rootly__getServiceUptimeChart for the last 30 days (if the MCP supports a period parameter; otherwise default).
  3. Call mcp__rootly__listIncidents with filter_service_ids=<id> and filter_status=started to surface active incidents on this service.
  4. If the service references an owning team, call mcp__rootly__getTeam for the team's name and mcp__rootly__get_oncall_schedule_summary (or mcp__rootly__get_oncall_handoff_summary) for current on-call.
  5. Optional: mcp__rootly__listIncidents filter by service in the last 90 days, page 1 only, to spot frequency.

3. Gather details — team path

If the resolved entity is a team:

  1. Call mcp__rootly__getTeam for the record. Capture name, description, slug, members count if available.
  2. Call mcp__rootly__listServices filtered by team to enumerate owned services.
  3. Call mcp__rootly__get_oncall_schedule_summary for current on-call across the team.
  4. Call mcp__rootly__listIncidents filtered by team and status=started for active incidents.

Read the full file on GitHub · 132 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.

  1. 9d ago First seen · 132 lines · 45 tokens per session scan A 88d4f004bc66

Subscribe to this mod's changes

lookup 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 45 tokens to every session and 1,173 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.

DevOps and cloud
Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens

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…

microsoft/vscode · 72 tokens