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 stakeholder-briefgit 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/stakeholder-brief)<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/stakeholder-brief"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/stakeholder-brief/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/stakeholder-brief"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/stakeholder-brief.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.00125 | $0.01931 |
| Opus 5 | $0.00063 | $0.00966 |
| Sonnet 5 | $0.00025 | $0.00386 |
| Haiku 4.5 | $0.00013 | $0.00193 |
Grade A, and why
stakeholder-brief 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder brief
Making technical facts usable by people who won't read the artifacts.
Why this exists
The FDE artifacts are written for engineers: cited, precise, and long. A sponsor will not read them, and shouldn't have to. But sponsors make the decisions that determine whether the work matters — funding it, prioritizing it, accepting the residual risk, approving the release.
So the facts have to travel, and travelling means changing form. Not simplifying to the point of uselessness, and not dumping the technical document with an apologetic summary on top, but genuinely re-writing for a reader whose question is "what do I need to do about this?"
There's a second function. An FDE has no track record here, and people calibrate on how you communicate long before they can judge your code. A brief that respects a busy reader's time and states its uncertainty honestly does more for your standing than the work it describes.
When this applies
- Phase boundaries — after recon, after feasibility, before a release
- A sponsor or delivery lead needs an update
- A decision is needed from outside the team
- Presenting assessment findings
- Bad news. Especially bad news.
When it doesn't
- Communicating with engineers — give them the artifact, they'd rather have the detail
- Nothing has changed and no decision is needed. A brief with no content trains people to skim the next one.
- A formal change submission — that's
release-readiness
Prerequisites
Whichever artifacts hold the current position. Read ../_shared/comms-register.md before writing — the register for each reader type is the substance of this skill.
Procedure
1. Identify the reader and what they can act on
Different readers need different documents from the same facts. From ../_shared/comms-register.md:
- Tech lead / architect — the options and the trade-off
- Delivery lead / EM — impact on plan, people, and date
- Sponsor / executive — the decision, the risk, the cost of being wrong
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 · 178 lines · 125 tokens per session scan A 130570b2aee9
stakeholder-brief is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 22d ago), licensed MIT. It adds 125 tokens to every session and 1,931 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.
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.