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.
npx skills add 85danf/agent-skills --skill plan-handoff-promptgit clone --depth 1 https://github.com/85danf/agent-skillsWrote 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.
[](https://agentmods.dev/skills/85danf/agent-skills/plan-handoff-prompt)<a href="https://agentmods.dev/skills/85danf/agent-skills/plan-handoff-prompt"><img src="https://agentmods.dev/badge/skills/85danf/agent-skills/plan-handoff-prompt/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.
<a href="https://agentmods.dev/skills/85danf/agent-skills/plan-handoff-prompt"><img src="https://agentmods.dev/badge/skills/85danf/agent-skills/plan-handoff-prompt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00048 | $0.01528 |
| Opus 5 | $0.00024 | $0.00764 |
| Sonnet 5 | $0.00010 | $0.00306 |
| Haiku 4.5 | $0.00005 | $0.00153 |
Grade A, and why
plan-handoff-prompt 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Handoff Prompt
Generate a stand-alone kickoff prompt that a fresh Claude session can paste-and-run to continue plan-driven work without re-deriving context. The output is a prompt the user pastes into a new session, not something the current session executes.
When to Use
- The user says "prepare a prompt I can give you in a fresh session", "kickoff prompt", "handoff prompt", "next-session prompt", or "draft the prompt for next time".
- The current session has finished a phase (plan written; tasks 1–N committed) and a follow-up phase will run separately.
- A plan file (and often a design/notes/spec file) exists under
docs/superpowers/.
Required inputs (ask only for missing; never invent)
- Phase verb —
picking up,running,implementing,executing,validating, orcontinuing. - Working directory — absolute path. Verify with
git -C <path> rev-parse --show-toplevel. - Current branch + main branch. Verify with
git -C <path> branch --show-currentandgit -C <path> symbolic-ref refs/remotes/origin/HEAD --short. Trust the user if the symref is unset. - Plan file path (relative to working dir). Required. Read first ~40 lines for task count and step style (
- [ ]checkbox vs free-form). - Companion design/notes/spec — optional. Include when present under
docs/superpowers/notes/or/specs/. Label by role: "canonical 'why' document", "design rationale", or "ground-truth spec". - Required state — commits or test counts next session confirms before starting. Get from
git log --oneline <base>..HEAD(last 10–20). Include commit-prefix convention (e.g.<JIRA-PREFIX> -) and the exactgit logcommand. - Required skill — usually
superpowers:subagent-driven-development(independent tasks, same session) orsuperpowers:executing-plans(parallel session). Match the plan's structure. - Friction notes — gotchas next session needs (stale .class files, IDE false positives, credential issues). Skip the section if none.
- Commit convention — JIRA prefix from branch name (
bugfix/<JIRA>-<slug>→<JIRA> - <message>), per the user's CLAUDE.md.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 90 lines · 48 tokens per session scan A fe886d503480
plan-handoff-prompt is a skill published in the GitHub repository 85danf/agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 1,528 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…