ring:creating-handoffs

ring:creating-handoffs is a skill for Cursor from LerianStudio/ring. It costs 93 tokens per session (719 once invoked), scanned A, original, Apache-2.0.

A handoff workflow that records the current session's completed work, decisions, unresolved items, and next steps in a document for another person or coding session. It also prepares the handoff so work can continue after the context is cleared.

In plain words
What is it for?
Use it when ending a session, switching to another developer or agent, saving progress for later, or preparing to continue after a context reset. It is unnecessary when the work is complete and nothing remains.
Why use it?
Important project context can be lost when a session ends or becomes too large to continue comfortably. A written handoff lets the next session resume without reconstructing the work from memory.

Skill for Cursor

Written for Cursor: shipped in a Cursor plugin. Also seen: names the ExitPlanMode tool; mentions Claude Code.

Part of the ring-default plugin — 23 skills, 2 agents, 1 hook shipped together

Good fit Use it when ending a session, switching to another developer or agent, saving progress for later, or preparing to continue after a context reset. It is unnecessary when the work is complete and nothing remains.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lerianstudio/ring/creating-handoffs
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 LerianStudio/ring --skill creating-handoffs
Clone the repo
git clone --depth 1 https://github.com/LerianStudio/ring

Made for: Cursor.

Or install ring-default, the plugin that ships this one along with the rest of its 23 skills, 2 agents, 1 hook.

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 ring:creating-handoffs

README.md
[![agentmods](https://agentmods.dev/badge/skills/lerianstudio/ring/creating-handoffs/github.svg)](https://agentmods.dev/skills/lerianstudio/ring/creating-handoffs)
Your own site
<a href="https://agentmods.dev/skills/lerianstudio/ring/creating-handoffs"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/creating-handoffs/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 ring:creating-handoffs

Your own site · 80×15
<a href="https://agentmods.dev/skills/lerianstudio/ring/creating-handoffs"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/creating-handoffs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 719 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Memory Poisoning · line 3
    Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
    Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
  • high Memory Poisoning · line 19
    Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
    Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
  • high Memory Poisoning · line 48
    Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
    Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
How audits are shown
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.00093 $0.00719
Opus 5.5 $0.00037 $0.00288
Sonnet 5.5 $0.00019 $0.00144
Haiku 4.5 $0.00009 $0.00072

Measured 1mo ago against content hash f00b99e508b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ring:creating-handoffs 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 1mo 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.

default/skills/creating-handoffs/SKILL.md · 102 lines

How it starts

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

Session Handoff Skill

When to use

  • User is ending a session and wants to preserve context for later
  • Context window is getting large and a fresh start would be beneficial
  • Handing off work to another person or AI session
  • User says "handoff", "save session", "wrap up", or "context transfer"

Skip when

  • Session has minimal context that does not warrant a handoff document
  • User simply wants to end the conversation without resuming later
  • Work is fully complete with nothing pending

Creates a handoff document capturing session context, delivered via Claude Code's Plan Mode so the user gets a native "clear context and continue implementing" option.

Execution Protocol (exact order, no skipping)

Step 1: Gather Context

Before entering plan mode, collect:

  • Completed work, decisions, and open items from conversation history
  • Use Glob and Read to verify file states and paths as needed
  • Use Bash with date for timestamps
  • Session name (from argument or infer from work done)

Step 2: Enter Plan Mode

Call EnterPlanMode tool.

Step 3: Write Handoff as the Plan

Write the full handoff document (template below) to the plan file path specified in the system message. The handoff IS the plan.

Step 4: Exit Plan Mode

Call ExitPlanMode tool — this presents the native resume options.

Step 5: Confirm to User

Handoff created and loaded as plan.

Choose "clear context and continue implementing" to resume in a fresh context.

Handoff Template

# Handoff: {Session Name}

**Created:** {timestamp}
**Session:** {session-name}
**Status:** {In Progress | Blocked | Ready for Review | Complete}

## Summary
{1-2 sentence overview}

## Current State
{Where things stand — specific about done vs pending}

## Completed Work
- {item with file references}

## In-Progress Work
- {partially done items — describe exactly where you stopped}

## Key Decisions
| Decision | Rationale | Alternatives Considered |
|----------|-----------|------------------------|

## What Worked
- {successful approaches worth reusing}

## What Didn't Work
- {failed approaches to avoid}

## Open Questions
- [ ] {unresolved questions or blockers}

## Next Steps
1. {First action when resuming — specific and actionable}

## Relevant Files
| File | Purpose | Status |
|------|---------|--------|

## Context for Resumption
{Gotchas, environment setup, branch state, test commands}

Read the full file on GitHub · 102 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. 1mo ago First seen · 102 lines · 93 tokens per session scan A f00b99e508b3

Subscribe to this mod's changes

ring:creating-handoffs is a skill published in the GitHub repository LerianStudio/ring (218 stars, last pushed today), licensed Apache-2.0. It adds 93 tokens to every session and 719 once invoked, about $0.0004 per session on Opus 5.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

incident

Incident response and postmortem generation from git/deploy context. When something breaks in production, this skill builds a timeline, identifies the probable cause, and generates a structured postmortem document. Flags: --since, --service, --sev, --revert, --comms, --dry-run.

greglas75/zuvo · 64 tokens

presentation

Generate PowerPoint (PPTX) presentations from a topic, outline, or content file. Creates professional slides using python-pptx with consistent theming and typography. Modes: [topic] (from scratch), from [file] (from markdown), --slides N, --theme dark|light|corporate, --outline-only, --out [path], --lang [code].

greglas75/zuvo · 80 tokens

antidote

Stop AI agents from patching symptoms. Use this skill when coding, reviewing, refactoring, auditing, committing fixes, or adding guards, validation, workarounds, or 20+ lines without deleting code.

Avtr99/antidote · 47 tokens

wheypoint

Mark the current conversation as a durable handoff so a new agent can resume the work. Use when the user wants to preserve state for a later or parallel session. Triggers include "hand this off", "write a handoff", "drop a wheypoint", "checkpoint this", "compact the conversation", and "/wheypoint". Also use for "wrap…

paulnsorensen/easy-cheese · 116 tokens

review

Structured code review with parallel audit agents, confidence-scored triage, and optional auto-fix. Examines uncommitted changes, staged diffs, commit ranges, or specific paths. Produces a tiered report (MUST-FIX / RECOMMENDED / NIT) backed by evidence, then optionally applies fixes with verification.

greglas75/zuvo · 70 tokens

write-tests

Write tests for existing production code. Processes ONE file at a time through a full pipeline: analyze, inventory (frozen BEFORE writing), write, executable coverage gate, verify, blind coverage audit, adversarial review, log. Uses CodeSift for discovery and analysis when available. Modes: [path] (specific target)…

greglas75/zuvo · 87 tokens