handoff

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

A document generator for transferring responsibility during an incident or on-call shift. An incident is a live service problem, while on-call is the role responsible for responding to such problems.

In plain words
What is it for?
Use it to prepare an incident handoff from an incident ID or create a general on-call shift summary.
Why use it?
It organizes the current situation, completed work, next steps, alerts, and contacts so the next person can take over quickly.

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

Good fit Use it to prepare an incident handoff from an incident ID or create a general on-call shift summary.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rootly-ai-labs/rootly-claude-plugin/handoff
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 handoff
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 handoff

README.md
[![agentmods](https://agentmods.dev/badge/skills/rootly-ai-labs/rootly-claude-plugin/handoff.svg)](https://agentmods.dev/skills/rootly-ai-labs/rootly-claude-plugin/handoff)
Your own site
<a href="https://agentmods.dev/skills/rootly-ai-labs/rootly-claude-plugin/handoff"><img src="https://agentmods.dev/badge/skills/rootly-ai-labs/rootly-claude-plugin/handoff.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 638 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.00024 $0.00638
Opus 5 $0.00012 $0.00319
Sonnet 5 $0.00005 $0.00128
Haiku 4.5 $0.00002 $0.00064

Measured 8d ago against content hash cc0f9e8cb993, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

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

skills/handoff/SKILL.md · 106 lines

How it starts

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

Incident & On-Call Handoff

You are preparing a handoff document for either incident response or on-call shift transitions.

Workflow

1. Determine Handoff Type

If $ARGUMENTS contains an incident ID:

  • Incident Handoff: Create handoff for specific incident
  • Call mcp__rootly__getIncident with the provided ID
  • Call mcp__rootly__listIncidentAlerts for associated alerts

If no incident ID provided:

  • On-Call Handoff: Create general shift handoff
  • Call mcp__rootly__get_oncall_handoff_summary or relevant on-call endpoints
  • Call mcp__rootly__search_incidents filtered to recent active incidents

2. Generate Incident Handoff

For incident-specific handoffs:

# Incident Handoff: [incident-title]

**Handoff Time**: [current-time]  
**Incident ID**: [short-id]  
**Severity**: [severity]  
**Current Status**: [status]  
**Started**: [started-at] ([duration] ago)

## Current Situation
[Brief summary of what's happening now]

## What's Been Done
- [action 1]
- [action 2]
- [action 3]

## Immediate Next Steps
1. [priority action]
2. [next action]
3. [monitoring action]

## Key Contacts
- **Incident Commander**: [if assigned]
- **On-Call**: [current on-call person]
- **Escalation Path**: [relevant escalation details]

## Important Notes
[Any critical context, gotchas, or special considerations]

## Monitoring
- [key dashboards/alerts to watch]
- [specific metrics to monitor]

3. Generate On-Call Handoff

For general on-call handoffs:

# On-Call Handoff

**Handoff Time**: [current-time]  
**Previous On-Call**: [if determinable]  
**Incoming On-Call**: [current/next on-call]

## Active Incidents
[List current active incidents with brief status]

## Recent Activity (Last 24h)
- [incident summaries]
- [any resolved issues]

## Ongoing Concerns
- [items requiring monitoring]
- [scheduled maintenance]
- [known issues]

## Escalation Paths
[Current escalation contacts and procedures]

## Key Dashboards
[Important monitoring dashboards to check]

## Upcoming Events
[Deployments, maintenance, or other scheduled activities]

Read the full file on GitHub · 106 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. 8d ago First seen · 106 lines · 24 tokens per session scan A cc0f9e8cb993

Subscribe to this mod's changes

handoff 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 24 tokens to every session and 638 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

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…

specstoryai/getspecstory · 126 tokens

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…

Donchitos/Claude-Code-Game-Studios · 77 tokens

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.

Orkas-AI/Orkas · 5 tokens

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.

wshobson/agents · 54 tokens