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 vunm-io/passdown --skill passdown-handoffgit clone --depth 1 https://github.com/vunm-io/passdownWrote 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/vunm-io/passdown/passdown-handoff)<a href="https://agentmods.dev/skills/vunm-io/passdown/passdown-handoff"><img src="https://agentmods.dev/badge/skills/vunm-io/passdown/passdown-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.1 | $0.00045 | $0.00995 |
| Opus 5 | $0.00023 | $0.00498 |
| Sonnet 5 | $0.00009 | $0.00199 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
passdown-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 7d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Passdown Handoff
End every working session with a passdown: a small file the next shift reads to catch up. State lives in files, never in the session.
Configuration (read first)
Build the effective passdown configuration root-to-nearest. Read applicable
AGENTS.md files from the workspace/repository root down to the current
directory, plus any parent file explicitly referenced by a thin entrypoint.
Merge ## passdown keys in that order: nearer values override the same key and
inherit omitted keys. Resolve relative paths against the file that declared
them.
The effective configuration should contain:
## passdown
- log_dir: <path for session logs>
- log_language: en # or another language for human-facing logs
If a required key is still missing, ask where session logs should live and
suggest adding it to the appropriate AGENTS.md.
Process
-
Create ONE new log file:
<log_dir>/YYYY-MM-DD_<short-topic>_<agent>-HHMMSS.md. Before writing, check whether the path already exists. On collision, add an incrementing suffix (-2,-3, ...) and create a new file; never truncate or append to another session's or agent's file. -
Start with machine-readable frontmatter, then the body sections (in the configured language). The frontmatter is what lets the next shift — or
passdown-pickup— filter logs without reading them in full:--- status: DONE # DONE | IN_PROGRESS | BLOCKED branch: <git branch> agent: <agent identity — the host name (claude|codex|kiro) unless the workspace names agents> plan: <path to the plan/change this session executed, or none> ---plan:paths must resolve from the workspace root — no repo shorthand, arrows, or prose, becausepassdown-pickupopens them mechanically. A session that executed several plans lists them all:plan: - repo-a/openspec/changes/slug-0004-short-name/ - repo-a/openspec/changes/slug-0009-short-name/
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.
- 7d ago First seen · 97 lines · 45 tokens per session scan A 6d433d9bf159
passdown-handoff is a skill published in the GitHub repository vunm-io/passdown (8 stars, last pushed 17d ago), licensed MIT. It adds 45 tokens to every session and 995 once invoked, about $0.0002 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
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
antigravity-skill-orchestrator
A meta-skill that understands task requirements, dynamically selects appropriate skills, tracks successful skill combinations using agent-memory-mcp, and prevents skill overuse for simple tasks.
agent-memory-mcp
A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
agent-memory
A hybrid memory system that provides persistent, searchable knowledge management for AI agents.
agent-memory-systems
Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector stores), and the cognitive architectures that organize them.
ai-agents-architect
Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration.