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 deploy-runbookgit 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/deploy-runbook)<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/deploy-runbook"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/deploy-runbook.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.00110 | $0.02584 |
| Opus 5 | $0.00055 | $0.01292 |
| Sonnet 5 | $0.00022 | $0.00517 |
| Haiku 4.5 | $0.00011 | $0.00258 |
Grade A, and why
deploy-runbook 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy runbook
The procedure someone else can execute under pressure.
Why this exists
Deployment knowledge in large organizations tends to live in one engineer's head, reconstructed each time from memory and a scroll through last quarter's chat history. That works until the deploy happens at 11pm on a Friday, or the engineer is on leave, or the person executing is a release manager who has never seen this service.
There's a second, sharper reason. A rollback plan that has never been executed is a hypothesis. The most common discovery during a real incident is that the migration wasn't reversible, or the rollback takes forty minutes, or it requires a permission the person on call doesn't have. All three are cheap to find out in advance and expensive to find out at the time.
When this applies
- First deploy of anything new or risky
- A change board or auditor needs a documented procedure
- The deploy path exists only in someone's head
- Anything with a migration, a flag, or coordination between components
When it doesn't
- Routine deploys through a mature, well-understood pipeline — don't add ceremony to something that works
- Local or throwaway environments
- A migration with a cutover window — that's
cutover-plan, which is a bigger artifact
Prerequisites
.fde/06-blast-radius-*.md— determines how careful the procedure must be.fde/07-verification.md— what's proven and what's a gap.fde/01-environment.md— the deploy commands, usually discoverable from CI.fde/08b-change-control.md— who may press the button, freeze windows, CAB ref. If missing, offerchange-control-navigationrather than inventing SoD.
Read the CI/CD configuration before writing anything. The existing pipeline is the real deploy path, and a runbook that contradicts it is worse than none.
A cutover window is cutover-plan (fde-migration). The observation window after a routine deploy is post-deploy-watch (fde-operate). If those packs are not installed, keep rollback and watch sections in this runbook and say so.
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 · 210 lines · 110 tokens per session scan A a3d1f2f952ec
deploy-runbook is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 20d ago), licensed MIT. It adds 110 tokens to every session and 2,584 once invoked, about $0.0006 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
consultancy-practices
Apply effective software quality consultancy practices. Use when consulting, advising clients, or establishing consultancy workflows.
haiku
When writing a haiku for this bot, follow these conventions.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
ln-62-repository-publisher
Commits, pushes, and remotely verifies authorized repository changes. Not for releases, package publication, or announcements.
remove
Remove a deployed framework or addon from the current workspace.