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 escalation-and-renegotiationgit 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/escalation-and-renegotiation)<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/escalation-and-renegotiation"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/escalation-and-renegotiation/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/escalation-and-renegotiation"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/escalation-and-renegotiation.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.00123 | $0.02015 |
| Opus 5 | $0.00062 | $0.01007 |
| Sonnet 5 | $0.00025 | $0.00403 |
| Haiku 4.5 | $0.00012 | $0.00201 |
Grade A, and why
escalation-and-renegotiation 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 11d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Escalation and renegotiation
Saying the difficult thing, early, in a way that gets acted on.
Why this exists
This is the hardest thing an FDE does, and the most consequential. Engagements are rarely judged on code quality. They're judged on whether the people paying for them felt informed and in control — and that is decided almost entirely by how you handle the moment when things stop going to plan.
Two failure modes, both common:
Waiting until certain. The instinct is to raise a problem only once you fully understand it and have a solution. By then the options that existed at first suspicion — re-scoping, adding help, resetting expectations while there's still time — have expired. The delivery lead loses those options without ever knowing they had them, and that is what damages trust, far more than the problem itself.
Escalating without evidence or a recommendation. Arriving with a problem and no analysis reads as complaining, and it transfers work to someone with less context than you.
The FDE's position makes both harder. You have no track record, you're often perceived as expensive, and you may be raising a problem the permanent team has already learned to live with.
When this applies
- The plan is no longer achievable
- A dependency has passed its expected date
- A requirement turns out to be wrong or unbuildable as specified
- You're being asked to commit to something you don't believe is deliverable
- A quality or safety concern is being deprioritized
- As soon as you suspect — not when you're certain
When it doesn't
- Normal in-flight variance you can absorb without affecting anything visible
- A technical decision within your remit — make it, record it in an ADR
- You haven't yet done the work to establish what's true. Spend an hour on that first; arriving with evidence is the whole difference.
- A routine status update with no decision needed — that's
stakeholder-brief
Prerequisites
.fde/00-engagement.md— who can actually decide- The artifact that holds the evidence (
04-feasibility.md,05b-estimate.md,00b-access.md, …) ../_shared/comms-register.mdbefore writing to anyone above tech lead
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.
- 11d ago First seen · 159 lines · 123 tokens per session scan A ec4d7922aa0c
escalation-and-renegotiation is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 24d ago), licensed MIT. It adds 123 tokens to every session and 2,015 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.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
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.
remove
Remove a deployed framework or addon from the current workspace.
ln-62-repository-publisher
Commits, pushes, and remotely verifies authorized repository changes. Not for releases, package publication, or announcements.
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.