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 OthmanAdi/MDDesign --skill session-handoffgit clone --depth 1 https://github.com/OthmanAdi/MDDesignWrote 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/othmanadi/mddesign/session-handoff)<a href="https://agentmods.dev/skills/othmanadi/mddesign/session-handoff"><img src="https://agentmods.dev/badge/skills/othmanadi/mddesign/session-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/othmanadi/mddesign/session-handoff"><img src="https://agentmods.dev/badge/skills/othmanadi/mddesign/session-handoff.svg" alt="Reviewed on agentmods" width="80" 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.00067 | $0.01253 |
| Opus 5.5 | $0.00027 | $0.00501 |
| Sonnet 5.5 | $0.00013 | $0.00251 |
| Haiku 4.5 | $0.00007 | $0.00125 |
Grade A, and why
session-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 1mo 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Handoff
Bridges sessions. The user's session ends; the next session picks up exactly where the last one left off.
SessionStart catchup
Triggered automatically by the SessionStart hook. Manually invokable via /mddesign:handoff catchup.
Step 1: Read planning files
Readtask_plan.mdif it exists. Note the active phase id and its bullets.Readfindings.mdif it exists. Note any## Design Contextblock.Readprogress.mdif it exists. Note the most recent### Phase <id> Resultand the most recent### Handoff <timestamp>entry.
Step 2: Read scratch
- Glob
.agents/memory/scratch/**/*.md. - For each scratch file, read the last ISO-timestamped entry.
Step 3: Recall last WHY
- Invoke
/memory-routerwith a query like "recent decisions for project ". - The router dispatches to MemPalace; returns the most recent WHY entries for this project.
Step 4: Synthesize the preamble
Build a one-paragraph (4-6 sentence) "where we left off" that names:
- The active phase and its current status
- The most recent decision (from WHY)
- Any open questions from the last
### Phase Result - Any in-flight scratch entries
Print this preamble to the user as your first message.
Step 5: Surface nudges
- If the project has UI files (
*.tsx|*.vue|*.svelte) but noDESIGN.md, print: "No DESIGN.md found. Run/mddesign:harvestto generate one." - If
task_plan.mddoes not exist, print: "No task_plan.md. Use planning-with-files to create one before starting work." - If
code-memory-routerslash command is not registered, print: "code-memory-router not detected. Memory operations will fall back to scratch only."
Stop promotion
Triggered automatically by the Stop hook. Manually invokable via /mddesign:handoff promote.
Step 1: Dispatch memory-keeper
Call the Agent tool with subagent_type: memory-keeper. Pass:
- A pointer to
progress.md(last 50 lines) - A pointer to
findings.md - A pointer to
.agents/memory/scratch/
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.
- 1mo ago First seen · 121 lines · 67 tokens per session scan A 87c3940eb09b
session-handoff is a skill published in the GitHub repository OthmanAdi/MDDesign (14 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 67 tokens to every session and 1,253 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
handoff
Generate a HANDOFF.md that captures goal, current state, files touched, failed attempts, and next steps — so a fresh Claude session can continue exactly where this one left off. Use when sessions are getting long, Claude keeps retrying the same broken solution, or the user wants to step away and resume later.
daily-briefing
Proactive daily briefing that fires on a recurring schedule, pulls recent memory and workspace context, composes a structured summary (action items, progress, radar, next steps), and delivers it to all active channels. Enable with a time like "set up my daily briefing at 9am". Disable, reschedule, or check status at…
context-preservation
State capture and restore across context window compactions. Monitors usage thresholds and serializes quality, task, and spec state for seamless continuation.
identity-snapshot
Generate a living profile of the user's working patterns, decision tendencies and quality preferences from their Dex data. Use when the user says 'what are my patterns', 'how do I work', or during week-review. Also use proactively when the model (older than 7 days) is stale. Not for planning a week; use week-plan.
instinct-review
Reviews/promotes/removes instincts from .claude/instincts/.md. Triggers: instinct review, curate instincts, manage instincts, promote instinct.
repeat
Runs prompt/slash command on recurring interval until done or limit. Triggers: repeat, recurring task, poll status, run every N minutes, interval.