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 enablement-handoffgit 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/enablement-handoff)<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/enablement-handoff"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/enablement-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/rpraharaj/forward-deployed-engineer/enablement-handoff"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/enablement-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.00105 | $0.02046 |
| Opus 5 | $0.00053 | $0.01023 |
| Sonnet 5 | $0.00021 | $0.00409 |
| Haiku 4.5 | $0.00011 | $0.00205 |
Grade A, and why
enablement-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 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enablement handoff
Leaving a team that can carry on.
Why this exists
handover-pack produces documents. Documents are necessary and they are not sufficient — a team can hold a complete, accurate handover pack and still be unable to operate what you built, because reading a runbook and having executed one are different states.
For many engagements the actual deliverable is a team that can continue. The code was never the point; the point was capability that persists. Where that's true and you optimize for shipping instead, you produce a technically successful engagement that decays the month you leave.
The mechanism that causes this is worth naming: an FDE working efficiently works alone, and every efficient solo week concentrates knowledge further. By the end you're the only person who understands the thing you were hired to make sustainable. Enablement has to be designed in from the middle of the engagement, because at the end it's too late.
When this applies
- An engagement is ending and the team must continue
- You've been building alone and knowledge has concentrated
- A team is inheriting something unfamiliar
- The real deliverable is capability, not code
- From the midpoint of the engagement, not the end
When it doesn't
- Genuinely throwaway work
- The receiving team already knows this domain better than you
- Nobody is receiving it — which is a finding to escalate, not a reason to skip this
- You need documents rather than capability — that's
handover-pack
Prerequisites
.fde/02b-ownership.md, .fde/01-environment.md, and any runbooks — you need to know who is inheriting this and what they must operate. Do not wait for 09-handover.md. Enablement starts at the midpoint; the handover is written at the end and links here.
Procedure
1. Work out what they must be able to do
Not "understand" — do. Concrete, verifiable capabilities:
- Run it locally and make a change
- Deploy it, and roll it back
- Diagnose the common failure
- Extend it in the way it's most likely to need extending
- Know when to ask for help, and whom
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 · 172 lines · 105 tokens per session scan A ee398c056049
enablement-handoff is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 21d ago), licensed MIT. It adds 105 tokens to every session and 2,046 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
good-docs-writing
Writing style guide derived from Modal's documentation voice. Apply when writing or editing docs, guides, tutorials, or technical prose that should read direct, second-person, confident, low-jargon, and example-first. Use to draft new docs in this voice or to revise existing prose toward it.
printing-press-retro
Use when the user asks to retro, run a retrospective, file findings, or improve the Printing Press after a printed-CLI run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings". Do not use for…
stride-analysis-patterns
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
blind-spot-pass
Use before starting work in a domain you don't know well, to surface the "unknown unknowns" — the things you don't even know to ask about — and learn just enough to prompt and decide well. Implements the "blind spot pass" pattern from Anthropic's Fable "finding your unknowns" field guide. Triggers when you say "I'm…
prompts-chat
Use when searching, installing, or improving AI skills and prompts via prompts.chat or skills.sh. Triggers on skill search, prompt lookup, install skill, improve prompt, prompts.chat.
memstack-marketing-webinar-script
Use this skill when the user says 'webinar script', 'webinar', 'live presentation', 'teach-to-sell', or needs a timestamped presentation script with slide notes, presenter cues, and replay email sequence. Do NOT use for launch plans or static sales page copy.