agentmods.dev

sdd-handoff

sdd-handoff is a skill for Claude Code from 3062-in-zamud/knowledgine. It costs 41 tokens per session (444 once invoked), scanned A, original, MIT.

A skill for creating a handoff report when work on a software specification moves between coding tools or sessions. The report records progress, decisions, deviations, checks, and next steps.

In plain words
What is it for?
Use it when moving work between Claude Code and Cursor, returning work for review, or ending a session before the specification is complete.
Why use it?
It reduces the context that gets lost when another developer or coding agent needs to continue unfinished work.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Claude Code.

not rated 3repo 1mo ago A scan 41 tokens original MIT

Good fit Use it when moving work between Claude Code and Cursor, returning work for review, or ending a session before the specification is complete.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/3062-in-zamud/knowledgine/sdd-handoff
View source ↗ 3062-in-zamud/knowledgine
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 3062-in-zamud/knowledgine --skill sdd-handoff
Clone the repo
git clone --depth 1 https://github.com/3062-in-zamud/knowledgine

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/sdd-handoff/github.svg)](https://agentmods.dev/skills/3062-in-zamud/knowledgine/sdd-handoff)
Your own site
<a href="https://agentmods.dev/skills/3062-in-zamud/knowledgine/sdd-handoff"><img src="https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/sdd-handoff/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 sdd-handoff

Your own site · 80×15
<a href="https://agentmods.dev/skills/3062-in-zamud/knowledgine/sdd-handoff"><img src="https://agentmods.dev/badge/skills/3062-in-zamud/knowledgine/sdd-handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 444 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.00041 $0.00444
Opus 5 $0.00020 $0.00222
Sonnet 5 $0.00008 $0.00089
Haiku 4.5 $0.00004 $0.00044

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

Security

Grade A, and why

sdd-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 12d 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.

.ai-agents/skills/sdd-handoff/SKILL.md · 58 lines

What it actually says

sdd-handoff

Purpose

Create a structured report that enables another AI tool (or a future session) to pick up implementation seamlessly. Eliminates context loss during tool transitions.

When to Use

  • Transitioning from Claude Code (planning) to Cursor (implementation)
  • Transitioning from Cursor back to Claude Code (for review or complex logic)
  • Ending a session with incomplete work

Arguments

  • $ARGUMENTS (optional): Spec ID (e.g., KNOW-001). If omitted, detect from current context.

Step-by-Step Instructions

  1. Identify the active spec from arguments or context (git branch name, recent files)

  2. Read current state:

    • specs/KNOW-{NNN}-*/tasks.md — count completed vs total tasks
    • specs/KNOW-{NNN}-*/requirements.md — acceptance criteria status
    • Current git branch and recent commits
    • pnpm verify result

  3. Collect decisions and deviations:

    • Any design decisions made during implementation
    • Any deviations from the original spec (and reasons)
    • Watch-out items or gotchas discovered

  4. Generate handoff report using the template from docs/workflows/handoff-template.md:

    • Spec location
    • Summary
    • Progress (tasks completed / total)
    • Branch name and base commit
    • Build status
    • Key decisions made
    • Deviations from spec
    • Watch-out items
    • Key files to focus on
    • How to continue (step-by-step)

  5. Output the report to the user. Optionally write to a file if requested.

Reference Files

  • docs/workflows/handoff-template.md — Report template
  • docs/workflows/sdd-overview.md — Tool role assignments
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. 12d ago First seen · 58 lines · 41 tokens per session scan A 06e928fa2b78

Subscribe to this mod's changes

sdd-handoff is a skill published in the GitHub repository 3062-in-zamud/knowledgine (3 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 444 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-31.

Building agentsPlanning
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

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

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens