Borrowing it
Nothing to install: this file belongs to aidemd-mcp/server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aidemd-mcp/server/main/.claude/skills/aide-handoff/SKILL.mdgit clone --depth 1 https://github.com/aidemd-mcp/serverWrote 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/aidemd-mcp/server/aide-handoff)<a href="https://agentmods.dev/skills/aidemd-mcp/server/aide-handoff"><img src="https://agentmods.dev/badge/skills/aidemd-mcp/server/aide-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.00226 | $0.01161 |
| Opus 5 | $0.00113 | $0.00580 |
| Sonnet 5 | $0.00045 | $0.00232 |
| Haiku 4.5 | $0.00023 | $0.00116 |
Grade A, and why
aide-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 6d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aide:handoff — Session Handoff
Record current pipeline state to .aide/session.aide. This skill owns the orchestration; the aide-spec-writer agent owns the actual file write (it transcribes orchestrator-supplied state into the canonical format). The aide-maintainer agent (NOT this skill) owns deletion at feature close. See session.aide spec for the file format.
Hard constraints
- You do NOT write
.aide/session.aideyourself. The actual file write belongs toaide-spec-writer. This skill describes the orchestration that surrounds the delegation. - You do NOT invent content. The invoking agent (orchestrator or other) holds the conversation context — current stage, settled decisions, where work paused, anti-regression invariants. That context is the content source. If the conversation doesn't supply it, ask before invoking the skill — never fabricate state.
- You do NOT delete
.aide/session.aide. That belongs toaide-maintainerat feature close. This skill is exclusively for create/update.
Checklist
- Detect operation mode. Read whether
.aide/session.aideexists:- File missing → CREATE mode (first handoff for the in-flight feature)
- File exists → UPDATE mode (apply a surgical diff to the existing log)
- Gather content from conversation context. Before delegating, identify the specific pieces
aide-spec-writerneeds:- For CREATE: feature intent (one line for the frontmatter
intent:field); state summary (current stage + what was just done + what's blocked);## Where this cycle stoppedcontent (the next agent's instructions); architectural decisions settled (numbered list, if any); anti-regression invariants (bullet list, if any); process discipline notes (optional); open questions (optional) - For UPDATE: change description (what transition occurred); section-targeted edits (e.g. "append decision #4: ...", "rewrite
## Where this cycle stoppedto: ..."); numbered references to preserve (decision #N stays stable across edits)
- For CREATE: feature intent (one line for the frontmatter
- Delegate to
aide-spec-writervia the Agent tool (subagent_type: aide-spec-writer). The delegation prompt MUST:- Name the operation type explicitly —
session.aide CREATEorsession.aide UPDATE. The spec-writer's default operation is.aidefrontmatter; naming the operation is mandatory for correct dispatch. - Quote all supplied content verbatim — the spec-writer transcribes; it never invents.
- Name the operation type explicitly —
- Receive the verdict — CREATED, UPDATED, or REFUSED.
- REFUSED on
session.aide already exists→ the orchestrator should have called UPDATE. Switch the operation type and re-delegate. - REFUSED on
session.aide missing→ the orchestrator should have called CREATE. Switch and re-delegate. - REFUSED on ambiguous prompt or missing load-bearing content (feature intent,
## Where this cycle stopped) → gather the missing content from conversation context (or ask the user if it's not in context) and re-delegate.
- REFUSED on
- Confirm completion and continue with whatever pipeline work was in flight before the handoff was invoked.
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.
- 6d ago First seen · 56 lines · 226 tokens per session scan A 8b8c4d63d271
aide-handoff is a skill published in the GitHub repository aidemd-mcp/server (3 stars, last pushed 3mo ago), licensed MIT. It adds 226 tokens to every session and 1,161 once invoked, about $0.0011 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
init-workspace-documentation
Skill "init-workspace-documentation" from griddynamics/rosetta, covering agent memory.md, agent memory, preventive rules, what worked and what failed.
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-reasoning
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.