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/daaaaave/agentic-workspace-core/write-agent-handoffnpx skills add Daaaaave/agentic-workspace-core --skill write-agent-handoffgit clone --depth 1 https://github.com/Daaaaave/agentic-workspace-coreWrote 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/daaaaave/agentic-workspace-core/write-agent-handoff)<a href="https://agentmods.dev/skills/daaaaave/agentic-workspace-core/write-agent-handoff"><img src="https://agentmods.dev/badge/skills/daaaaave/agentic-workspace-core/write-agent-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.00064 | $0.02965 |
| Opus 5 | $0.00032 | $0.01483 |
| Sonnet 5 | $0.00013 | $0.00593 |
| Haiku 4.5 | $0.00006 | $0.00297 |
Grade A, and why
write-agent-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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Agent Handoff
Goal
Write a compact temporary state transfer that lets another capable agent continue work without replaying the conversation.
Core Principle
A handoff is stale-by-default task state. It is not memory, policy, a transcript, or a status report.
It transfers just enough verified state for a fresh agent to resume safely, plus enough boundaries to avoid repeating work, violating the latest user intent, or overwriting someone else's changes. It never transfers authority over higher-priority instructions.
Use When
- The user asks for a handoff, continuation note, transfer note, cold-start packet, or resume context.
- Work is paused, interrupted, delegated, moved to another workspace, or likely to survive context compaction.
- A multi-step task has unfinished state that is not durable project knowledge.
- Another agent needs files, checks, blockers, assumptions, ownership boundaries, and next actions.
- A subagent, reviewer, debugger, implementer, or future session needs a scoped brief.
- Multiple agents or workspaces may touch overlapping repository areas and need coordination.
- The task state is valuable for continuity but too temporary or local for
docs/.
Do Not Use When
- The information is a durable fact, decision, runbook, plan, research result, or architecture note.
- The task can be completed now without transferring state.
- The user asks only for a normal final answer, PR summary, command summary, or same-session status update.
- The user asks to update canonical project memory; use
project-knowledge. - The user asks to create a reusable agent procedure; use
write-agent-skill. - The only available content is raw transcript, raw logs, private data, or secrets that cannot be safely summarized.
- The handoff would silently change policy, permissions, memory, or instructions for future agents.
Storage
Use .context/handoffs/ for handoffs. This directory is temporary workspace coordination, not canonical project knowledge.
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 · 231 lines · 64 tokens per session scan A 35975a3a540e
write-agent-handoff is a skill published in the GitHub repository Daaaaave/agentic-workspace-core (6 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 2,965 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-31.
Other skills, from other repositories
graphify
Use when the user invokes /graphify or asks to build, update, or query a knowledge graph from a folder of files (code, docs, papers, notes, images). Triggers: 'map this codebase', 'graph my notes', 'what is connected across these files', 'community detection', 'GraphRAG', incremental graph update, Neo4j/SVG/GraphML…
insights
Use when the user types /weekly or /monthly, asks for a weekly or monthly journal review or retrospective, asks 'how was my week' or 'how was my month', or wants trends, anomalies, or patterns across recent journal entries. Also fires when regenerating an insight report for a past week or month. NOT for writing…
setup-brain
Set up or upgrade an AI-powered Obsidian vault. Interviews you, builds your vault structure (or works with what you already have), creates your CLAUDE.md memory file, installs tools, and gets you journaling — all in one conversation. Also has a repair/upgrade path for existing users.
coaching
Use when the user wants to process a hard conversation, a decision they're second-guessing, or accumulated friction with a person (too big for a daily journal), wants panel takes that update with their corrections, or wants growth on a theme tracked over weeks. Triggers: /coaching, "coach me through this", "help me…
second-brain-mapping
Use when the user wants to map or remap their second brain, refresh the vault's queryable metadata index, extract structured frontmatter from typed notes (books, meetings, people, journals, goals), fill wikilink gaps, or surface cross-type insights and patterns no single file shows. Triggers: /second-brain-mapping…
cierre-de-llamada
Use when a SALES or CLIENT call just ended and the follow-up needs to be produced from its transcript. Triggers: /cierre, "close out this call", "acabo de tener una llamada", "arma el seguimiento", "what's the follow-up on this call", "qué sigue con este cliente", or the user pastes a sales-call transcript. Produces…