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 agentmods add skills/promptpartner/agentsmith/handoffnpx skills add PromptPartner/agentsmith --skill handoffgit clone --depth 1 https://github.com/PromptPartner/agentsmithWrote 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/promptpartner/agentsmith/handoff)<a href="https://agentmods.dev/skills/promptpartner/agentsmith/handoff"><img src="https://agentmods.dev/badge/skills/promptpartner/agentsmith/handoff.svg" alt="Measured on agentmods" 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 | $0.00066 | $0.00601 |
| Opus 5 | $0.00033 | $0.00300 |
| Sonnet 5 | $0.00013 | $0.00120 |
| Haiku 4.5 | $0.00007 | $0.00060 |
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 4d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff — memory first, then the kickoff
A fresh session has zero memory of this one; the handoff note is the only bridge. Run this whenever work winds down — even if no one asked (core/50).
When this fires
"handoff" / "wrap up" / "let's stop here" / "I'm running low on context" / a phase or task just closed.
Runtime neutrality
This workflow is identical in every client. Never infer the active agent from this skill's install
path: .agents/skills is the shared Agent Skills location. Use “fresh chat” rather than a
runtime-specific reset command so the note remains portable.
Fast path — if the Agentsmith CLI is available
- Run
agentsmith handoff [item-id]— use.agentsmith/agentsmithon macOS/Linux or.agentsmith\\agentsmith.cmdon Windows when the command is not on PATH. It pre-fills branch/HEAD/dirty count and scaffolds.harness/handoffs/handoff-<stamp>.mdwith the standard sections. - Fill the scaffolded sections (below), then emit the kickoff block as your final message.
Fallback — no CLI
- Safe state FIRST (core/50 step 1): commit or stash so nothing half-edited is lost. Never hand off a dirty tree silently.
- Write
.harness/handoffs/handoff-<stamp>.mdwith these sections:- What shipped this session — with commit SHAs / PR links.
- What is still pending.
- Deviations / decisions made (so they're not re-litigated).
- Exact next step — the single first action for the next session.
- Gotchas a fresh session would otherwise re-derive.
- Emit a fenced "Kickoff prompt for a fresh chat" block: 3–6 sentences of self-contained prose (not bullets — they paste it straight in) covering the item id, branch + HEAD, what's done, the single next step, decisions already made, and the handoff note path.
Report
Name the handoff file, then end your message with the fenced kickoff block. If you notice mid-wrap that you haven't written the note yet, stop and write it before continuing.
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.
- 4d ago First seen · 43 lines · 66 tokens per session scan A e55adf281bf9
handoff is a skill published in the GitHub repository PromptPartner/agentsmith (188 stars, last pushed 4d ago), licensed MIT. It adds 66 tokens to every session and 601 once invoked, about $0.0003 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-30.
Other skills, from other repositories
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
nw-at-completeness-check
Canonical AT completeness gate — research-anchored 7-category taxonomy (C1-C7) + 15-item mechanical checklist. Paradigm-neutral. Drives acceptance-designer reviewer verdict deterministically.
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…
kelos
Author, debug, and operate Kelos resources (Task, Session, Workspace, AgentConfig, TaskSpawner) on Kubernetes. Use for Kelos CRDs, resource manifests, the kelos CLI, or live cluster operations. Do not use for ordinary Kelos repo code edits, tests, reviews, build/CI, or git tasks unless they involve those resources.
arch-save
Save an architect's state, clear its context, and re-init automatically — the packaged save→clear→re-init refresh cycle. Use when the owner directs a context refresh, or says "/arch-save", "save and clear", "refresh your context". Runs on the owner's direction; an architect does not invoke it autonomously mid-task.…