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 anton-abyzov/specweave --skill handoffgit clone --depth 1 https://github.com/anton-abyzov/specweaveWrote 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/anton-abyzov/specweave/handoff)<a href="https://agentmods.dev/skills/anton-abyzov/specweave/handoff"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/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/anton-abyzov/specweave/handoff"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
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 →
- medium Agent Snooping · line 31 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 41 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium MCP Rug Pull · line 41 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00051 | $0.01983 |
| Opus 5.5 | $0.00020 | $0.00793 |
| Sonnet 5.5 | $0.00010 | $0.00397 |
| Haiku 4.5 | $0.00005 | $0.00198 |
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 3d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sw-handoff: "hand off" here, "pick up" there
The user should never have to copy a prompt. Two words each way.
Hand off
When the user says "hand off", "handoff", "I'm out of tokens", "switching to Codex" or "switching accounts", run:
specweave handoff --reason "<their words>"
It releases your task claims, records the handoff in the ledger, writes handoff.md
next to the increment, pushes the branch, and pushes a snapshot of your uncommitted
edits to the specweave-handoff branch (and wip/<branch>). Your working tree,
index and branch are untouched. Relay its two or three lines as they are, then tell
the user: say "pick up" in the other tool.
Before handing off, make sure your last task claim / task done carried --line
(the card text) and, for done work, --link (PR, report or artifact); the next agent
reads the checklist, not your transcript.
Add --next "<exact next step>", --gotcha "..." or --decision "..." only for what
the files cannot tell the next agent. No Git remote and another machine:
--inline prints a prompt to paste instead. --no-push keeps it local.
Hand off everything (switching accounts with many threads)
When the user switches accounts or tools with several increments in flight ("hand off all", "switching subscriptions"), run:
specweave handoff --all --reason "<their words>"
It writes .specweave/handoffs/<date>-INDEX.md and index.json: one row per active
increment (tasks done/total, open ACs, last activity, what it waits on, a paste-ready
resume prompt) and, in an umbrella workspace, every checkout under
repositories/<org>/<repo> (and its worktrees) with uncommitted files, unpushed
commits or a branch with no remote, with its open PR when gh is installed. It is
read-only toward everything else: no claims released, nothing committed or pushed in
the umbrella or the nested repos. Commit and push the local-only work it lists, or say
so in your reply. --dry-run prints the index without writing it.
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.
- 3d ago Changed · +8 lines f67c9350dcc7
- 7d ago Changed 080446b27b46
- 12d ago Changed · +14 lines 78bf1802be59
- 13d ago Changed · -1 lines 0be8e7f7364b
- 14d ago Changed · +8 lines 56e034920647
- 19d ago Changed · +37 lines · +5 tokens per session 411d063b9dd8
- 27d ago Changed · +34 lines · +2 tokens per session 42a03b6bca7f
- 1mo ago First seen · 42 lines · 44 tokens per session scan A f1f0fd1a35f3
handoff is a skill published in the GitHub repository anton-abyzov/specweave (167 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 1,983 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-03.
Other skills, from other repositories
gws-workflow-email-to-task
Google Workflow: Convert a Gmail message into a Google Tasks entry.
gws-workflow-standup-report
Google Workflow: Today's meetings + open tasks as a standup summary.
mvp-plan
Plan the MVP build from a PRD and an MVP scope, as a full development plan or an ultra-lean build spec, with the AI Product Development Toolkit's planning prompts.
prd
Interview the owner about a product idea, then draft a Product Requirements Document (PRD) with the AI Product Development Toolkit's PRD prompt.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
hatch3r-cleanup
Repo-state cleanup pass — inventories accumulated hatch3r working state (plan files, workspace dirs, review telemetry, findings ledgers, learnings, handoffs, board staleness), asks once with per-category counts and estimated reclaim, dispatches each owned surface to its owning skill or CLI path, and prunes only the…