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 brunob54/superpowers-orchestrator --skill handoffgit clone --depth 1 https://github.com/brunob54/superpowers-orchestratorWrote 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/brunob54/superpowers-orchestrator/handoff)<a href="https://agentmods.dev/skills/brunob54/superpowers-orchestrator/handoff"><img src="https://agentmods.dev/badge/skills/brunob54/superpowers-orchestrator/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.
<a href="https://agentmods.dev/skills/brunob54/superpowers-orchestrator/handoff"><img src="https://agentmods.dev/badge/skills/brunob54/superpowers-orchestrator/handoff.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.00046 | $0.01392 |
| Opus 5.5 | $0.00018 | $0.00557 |
| Sonnet 5.5 | $0.00009 | $0.00278 |
| Haiku 4.5 | $0.00005 | $0.00139 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff
The user is about to clear the context window. Produce a prompt that lets a fresh session, which starts with zero memory of this one, continue the work without re-deriving anything this session established.
Today's date, time and time-zone offset: !date +%FT%H:%M%z
Current branch and HEAD: !git branch --show-current 2>/dev/null | grep . || echo none at !git rev-parse --short HEAD 2>/dev/null || echo none
Uncommitted files: !git status --short 2>/dev/null | wc -l | tr -d ' '
Argument given by the user (may be empty): $ARGUMENTS
Procedure
-
Decide the slug. If the user gave an argument, use it (lower-case, hyphens). Otherwise derive a short slug from the next work item (the row number or feature name the next session will work on). The file is
tmp/docs/<today>-handoff-<slug>.md, where<today>is the date part (YYYY-MM-DD) of the date and time printed above. Createtmp/docs/if it does not exist. Never overwrite an existing file: if the name is taken, append-2. -
Collect the facts, mostly from files, not from memory. Every source below is optional; use the ones the project has. Read
state.mdand the last two[saved]entries ofsession-log.md(written by the context-management skill in projects where state was saved); the previous handoff intmp/docs/(the newest*handoff*file) for the conventions section, or the project'sCLAUDE.mdwhen there is no previous handoff; the version file and the installed version if the project publishes a package or plugin; the project's worklist or issue file ifstate.md, the previous handoff orCLAUDE.mdnames one (the item the next session works on). Delegate bulk reads to a subagent; keep this window small. -
Write the prompt with exactly these sections, in plain English, no idioms, every technical term defined at first use, lines at most 88 columns:
- Header line. The file's first line is exactly
Handoff: written=<YYYY-MM-DD>T<HH:MM><+hhmm> branch=<name|none> head=<short sha|none>, with the values printed above (<+hhmm>is the time-zone offset, such as+0200;<short sha>is the short commit id;nonefor an empty value). The /pickup skill reads it to find the newest handoff and the commits made after it. When the next task has an end state that a commit may not show, the second line isDone when: <one checkable condition>. - Opening paragraph. The task in one or two sentences, naming the row or feature and the file and line where it is described; the repository, the branch, the version, whether the tree is clean, and whether the installed plugin matches main.
- ## What is already known (do not re-derive). Every fact this session verified that the next session would otherwise have to re-measure: figures, with the transcript ids or file:line they came from; decisions the user made, stated as decisions; contradictions found between documents and evidence; what was rejected and why, in one line each; the exact commands that produced key evidence when they were not obvious. Facts only, each with its source.
- ## How to proceed. Numbered steps, in the order the next session should take them. Name the design step when one is needed (independent lenses plus a rebuttal round before tallying), the point where the user decides, and the delivery shape (spec plus orchestrated run, or a direct change on a feature branch with assertions first). Name every fast test suite to run.
- ## Conventions that bit us. The repository rules that cost time in this or earlier sessions: forbidden words, line budgets, merge style, the full release checklist with every file to bump, the issues-log rules, the save-state rule. Carry forward the previous handoff's list and add what this session learned; drop nothing unless it is no longer true.
- Closing reminders after the sections: uncommitted files, background agents still running, a CLI restart owed after a plugin update, files that are local and untracked.
- Header line. The file's first line is exactly
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.
- 1mo ago First seen · 95 lines · 46 tokens per session scan A 13e558ef7107
handoff is a skill published in the GitHub repository brunob54/superpowers-orchestrator (3 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,392 once invoked, about $0.0002 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-09-16.
Other skills, from other repositories
assess
Issue triage and status assessment - analyze current state, detect health signals, and recommend next action with full workflow plan.
release
Automates the full release workflow: version bump, git tag, GitHub release, and npm publish.
solve
Deprecated: alias for /assess. Generate the recommended workflow for one or more GitHub issues.
reflect
Strategic reflection on workflow effectiveness and continuous improvement.
add-teams
Adds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat.
sys-configure
Configure Claude Octopus — redirects to /octo:setup interactive wizard.