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 rpraharaj/forward-deployed-engineer --skill handover-packgit clone --depth 1 https://github.com/rpraharaj/forward-deployed-engineerWrote 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/rpraharaj/forward-deployed-engineer/handover-pack)<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/handover-pack"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/handover-pack.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.00091 | $0.02269 |
| Opus 5 | $0.00046 | $0.01135 |
| Sonnet 5 | $0.00018 | $0.00454 |
| Haiku 4.5 | $0.00009 | $0.00227 |
Grade A, and why
handover-pack 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 8d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handover pack
Making the work outlive you.
Why this exists
An FDE leaves. That's the defining feature of the role, and it means an engagement is only as valuable as what remains after you go.
The default handover is a meeting and a link to a branch. Three months later the team has drifted from the design, doesn't know why a decision was made, has re-broken something you fixed, and is quietly working around a flag nobody dares remove.
The section that matters most is the one almost every handover omits: the open risks and unfinished business. Handovers get written to look like successful conclusions, so the awkward parts — the untested rollback, the consumer who never replied, the assumption nobody validated — get smoothed away. Those are precisely what the receiving team needs, and precisely what they can't reconstruct.
When this applies
- An engagement is ending or you're rotating off
- Someone else takes over work in progress
- A contract or phase boundary
- Two weeks before you leave, not in the final days
When it doesn't
- Short engagements where the artifacts already are the handover — point at
.fde/and walk them through it - Work that will genuinely never be touched again, which is rarer than it seems
- Teaching the team to operate what you built — that's
enablement-handoff, and it's a different activity that should happen alongside this
Prerequisites
The .fde/ workspace. This skill consolidates rather than creates — if the artifacts were kept as you went, this is an afternoon. If they weren't, it's a week, and it'll be worse.
Procedure
1. Start two weeks out
The single most important instruction. A handover written in the final days is rushed, and the final days are exactly when people want your time for other things.
Starting early also means you can test it: give it to someone and watch them try to use it. Every gap they hit is one you can still close.
2. Identify who's actually receiving it
Handovers written for a generic reader help nobody. Establish specifically: who maintains this now, what do they already know, and what have they never seen?
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.
- 8d ago First seen · 198 lines · 91 tokens per session scan A 895ca45fb407
handover-pack is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 21d ago), licensed MIT. It adds 91 tokens to every session and 2,269 once invoked, about $0.0005 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
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…
product-manager-toolkit
Use when the user needs product management workflows such as RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, go-to-market strategy, feature prioritization, research synthesis, or requirements documentation.
ijfw-workflow
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…