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 decommission-plangit 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/decommission-plan)<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/decommission-plan"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/decommission-plan/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/decommission-plan"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/decommission-plan.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.00097 | $0.02513 |
| Opus 5 | $0.00048 | $0.01256 |
| Sonnet 5 | $0.00019 | $0.00503 |
| Haiku 4.5 | $0.00010 | $0.00251 |
Grade A, and why
decommission-plan 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 9d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decommission plan
Proving nothing needs it, then turning it off.
Why this exists
Decommissioning is common, genuinely hard, and almost never planned properly. Systems get left running for years after their replacement ships because nobody was willing to say it was safe to stop them — which is a rational position, since the evidence to say so was never gathered.
The difficulty is entirely in one place: proving there are no remaining consumers. Turning something off takes a minute. Knowing you can is the work, and it's hard because absence of evidence is not evidence of absence. A quarterly report, an annual regulatory extract, or a partner integration used twice a year will not appear in a week of traffic logs.
The second reason this matters: leaving systems running has real costs — licences, infrastructure, patching obligations, audit scope, and the ongoing confusion of two systems where one is authoritative. Nobody attributes those costs to the decommission that didn't happen.
When this applies
- A system is being retired
- After a migration leaves the old system idle
- "Can we switch this off?"
- A service appears unused
- Cost or audit-scope reduction
When it doesn't
- The replacement isn't live and proven yet — finish
cutover-planfirst - Deleting code rather than retiring a running system — that's
safe-changeplusgit-archaeology - You're being asked to prove something is unused with no authority to act — that's an assessment
Prerequisites
- Locate the workspace:
FDE_WORKSPACE, else the charter Location, else.fde/, else../<repo>-fde/ .fde/02-system-map.mdand.fde/02b-ownership.md.fde/runbooks/cutover-*.mdif this follows a migration- Access to logs, monitoring, and network data covering at least a full business cycle
Procedure
1. Establish what "off" means
Several distinct states, and conflating them causes most of the confusion:
| State | Meaning | Reversible |
|---|---|---|
| Read-only | Still serves reads, accepts no writes | Trivially |
| Dark | Running, no traffic routed | Trivially |
| Stopped | Not running, data intact | Minutes to hours |
| Deprovisioned | Infrastructure released, data archived | Days, if archived properly |
| Deleted | Data gone | Never |
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.
- 9d ago First seen · 190 lines · 97 tokens per session scan A a8f5d9e83c1f
decommission-plan is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 22d ago), licensed MIT. It adds 97 tokens to every session and 2,513 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
consultancy-practices
Apply effective software quality consultancy practices. Use when consulting, advising clients, or establishing consultancy workflows.
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.
maggy
Maggy is a local AI engineering command center. AI-prioritized inbox across issue trackers (GitHub Issues/Asana), one-click TDD execute with iCPG context enrichment, daily competitor intelligence briefing.