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 dependency-upgradegit 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/dependency-upgrade)<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/dependency-upgrade"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/dependency-upgrade.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.00105 | $0.02182 |
| Opus 5 | $0.00053 | $0.01091 |
| Sonnet 5 | $0.00021 | $0.00436 |
| Haiku 4.5 | $0.00011 | $0.00218 |
Grade A, and why
dependency-upgrade 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency upgrade
Work where you don't get to choose the scope or the date.
Why this exists
EOL-driven work — a runtime going out of support, a framework major version, a database version, an expiring vendor contract — is an enormous share of enterprise IT and it behaves unlike feature work in three ways:
- Scope is fixed. You can't descope your way out of Java 8 losing support.
- The deadline is external. Nobody in the organization can move it.
- The risk is transitive. The library you're upgrading is fine; the four things depending on it are the problem, and they surface one at a time.
Planned like a feature, it goes wrong predictably: an estimate based on the direct change, then weeks of cascading incompatibilities nobody sized. The work isn't the upgrade. It's the fallout.
The compensating advantage: it's unusually amenable to systematic treatment. The compatibility matrix is knowable up front, and most of the pain comes from not building one.
When this applies
- End-of-life: runtime, framework, database, OS, vendor product
- Major version jumps
- Security-driven bumps that cascade
- A library upgrade pulling in more than expected
When it doesn't
- Routine patch bumps handled by automation
- The upgrade is genuinely one line and the tests pass — just do it
- Replacing rather than upgrading — that's
refactor-seamsor a migration
Prerequisites
- Locate the workspace:
FDE_WORKSPACE, else the charter Location, else.fde/, else../<repo>-fde/ .fde/02-system-map.md.fde/01-environment.md— you need a working build before changing what it builds withcharacterization-testswhere coverage is thin. An upgrade with no tests is a rewrite you can't verify.
Procedure
1. Establish the real deadline and what happens after it
"End of life" means different things and the difference matters enormously to how much leverage you have:
- No more feature releases — soft
- No more security patches — hard for most compliance regimes
- Vendor refuses support tickets — hard operationally
- Service actively stops working — hard, absolute
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 · 182 lines · 105 tokens per session scan A 2e8620ea2f53
dependency-upgrade is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 20d ago), licensed MIT. It adds 105 tokens to every session and 2,182 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.
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.