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/mathews-tom/armory/handoffnpx skills add Mathews-Tom/armory --skill handoffgit clone --depth 1 https://github.com/Mathews-Tom/armoryWrote 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/mathews-tom/armory/handoff)<a href="https://agentmods.dev/skills/mathews-tom/armory/handoff"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/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.00115 | $0.01512 |
| Opus 5 | $0.00057 | $0.00756 |
| Sonnet 5 | $0.00023 | $0.00302 |
| Haiku 4.5 | $0.00012 | $0.00151 |
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 5d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff
Maintains .docs/handoff.md as the project-local cold-start primer for the next coding agent or human developer. The file captures transient session state only: what changed, what was decided, what is blocked, and exactly how to resume.
Reference Files
| File | Contents | Load When |
|---|---|---|
references/schema.md |
Verbatim handoff schema and line-budget rules | Always before writing |
references/authority-boundaries.md |
Boundary between handoff, memory, CLAUDE.md, plans, and git | Always before writing |
When To Use
| Use handoff | Use another surface |
|---|---|
| In-flight work, uncommitted edits, current branch, blockers, resume steps | git log for committed history |
| Session-scoped decisions and failed approaches | Memory or ADRs for durable project facts |
| Immediate validation state and exact next command | CLAUDE.md for stable setup instructions |
| Current roadmap cursor | Plan files for strategic roadmap content |
Triggers
- Direct commands:
/handoff,/handoff init - Refresh phrases: "update handoff", "session handoff", "refresh handoff", "save handoff"
- Resume phrases: "cold-start primer", "resume checklist", "handoff to next session"
- Stop hook: refresh silently when
.docs/handoff.mdalready exists
Prerequisites
gitavailable in the project root.- Project write access for
.docs/handoff.md. - Optional project-local marker files:
.docs/handoff.last-validationcontaining the last verification command and result..docs/handoff.sessioncontaining extra bullets for changes, decisions, blockers, or refs.
Workflow
- Resolve mode.
/handoff initor invocation from an initialization workflow writes a greenfield stub when.docs/handoff.mdis absent./handoff, refresh phrases, and Stop-hook invocation rewrite the full file.
- Read source of truth.
- Load
references/schema.mdand preserve the schema headings exactly. - Load
references/authority-boundaries.mdand include the authority boundary line in every generated handoff.
- Load
- Detect repository state.
- Run
git rev-parse --show-toplevel,git branch --show-current,git rev-parse --short HEAD, andgit status --porcelain. - Count modified, untracked, and staged paths from porcelain status.
- Include the top 3-5 changed paths in the Status section.
- Run
- Detect validation state.
- Prefer recent session context: commands actually run in the current agent session and their result.
- If available, read
.docs/handoff.last-validation. - If neither exists, write explicit unknowns: "not recorded this session" rather than inventing pass/fail.
- Gather session substance.
- Summarize logical changes from current conversation, uncommitted paths, and commits since the branch base when relevant.
- Record decisions with rationale in two sentences or fewer.
- Record blockers and open questions as actionable unchecked items.
- Include failed approaches when they would prevent wasted work in the next session.
- Write by full rewrite.
- Replace
.docs/handoff.mdatomically; do not append. - Create
.docs/if absent. - Keep the file lowercase at
.docs/handoff.md.
- Replace
- Enforce 200 lines.
- Count final lines after rendering.
- If over 200, truncate
## What changed this sessionoldest-first. - Insert
<!-- WARNING: handoff exceeded 200 lines; oldest session changes were truncated. -->. - If still over 200, compress decisions and blockers to the newest actionable items, preserving all required headings.
What ships with it
6 files 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.
- 5d ago First seen · 137 lines · 115 tokens per session scan A c0350d96dc79
handoff is a skill published in the GitHub repository Mathews-Tom/armory (316 stars, last pushed 7d ago), licensed MIT. It adds 115 tokens to every session and 1,512 once invoked, about $0.0006 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
openagentskill-registry
Discover, compare, audit, and safely install reusable AI Agent Skills with OpenAgentSkill. Use whenever an agent needs a capability it does not already have, must compare Skill alternatives, or needs evidence before installing third-party instructions.
manager
Sync session work into GitHub issues, or query track status across repos. Write: find/update issue + W-label. Read: "что по ". Triggers: "создай issue", "синкни сессию", "manager". Not day/week plans (daily-tasks).
weekly-retro
Use when the user is closing an ISO week, reviewing planned outcomes against evidence, interviewing work Areas, resolving unfinished commitments, or asking for "ретро", "weekly retro", "week review", or lessons from the week.
art-director
Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.
corp-doctor
Use when a Personal Corp operating loop needs setup, repair, a new department, or task routing: HQ files and agent rules, GitHub issue workflow, corp- owner map, department repositories, or deciding which repo an issue belongs to. Triggers: "corp doctor", "почини контур", "заведи отдел", "куда положить задачу"…
html-draft
Use when user wants a standalone HTML diagram in flat engineering blueprint style — architecture diagrams, system flows, technical spec sheets, component maps. Generates one HTML file using Tailwind v4 (browser CDN) for layout and D3 v7 (CDN) for SVG diagrams. User-invoked only — do NOT auto-trigger. Triggers on…