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 release-readinessgit 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/release-readiness)<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/release-readiness"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/release-readiness.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.00128 | $0.02571 |
| Opus 5 | $0.00064 | $0.01286 |
| Sonnet 5 | $0.00026 | $0.00514 |
| Haiku 4.5 | $0.00013 | $0.00257 |
Grade A, and why
release-readiness 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 8d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release readiness
Turning accumulated evidence into a defensible go/no-go.
Why this exists
Release decisions in large organizations are usually made on vibes and seniority. Someone asks whether we're ready, the people closest to the work say they think so, and the residual uncertainty — which is real, and which someone privately knows about — never makes it into the room.
Then it fails, and the post-incident review discovers that three people each knew one piece of it.
This skill exists to make the uncertainty explicit at the moment the decision is made. Its distinguishing property is that it refuses to launder uncertainty. A recommendation of "go" with three unverified items says so, in the recommendation, where the approver reads it. That's what makes it worth anything: an assessment that always says yes carries no information.
It also happens to be the fastest way for an FDE to build trust. An engineer who says "no, and here's exactly what's missing" once is believed when they say yes.
When this applies
- Approaching go-live on anything non-trivial
- A CAB, stage gate, or formal approval is required
- "Are we ready to ship?"
- You think the answer is no and need the reasoning to survive scrutiny
- A release decision is being made and nobody has assembled the evidence
When it doesn't
- Routine low-risk deploys in a mature pipeline — don't add ceremony to a well-managed process
- Emergency mitigation during an incident, where the calculus is different and explicit
- You have no evidence to assemble. Then the honest output is "we can't assess this yet, and here's what's needed" — which is itself a legitimate and useful finding.
Prerequisites
This skill gathers; it doesn't re-derive. It reads:
| Artifact | Provides |
|---|---|
03-requirements.md |
The acceptance criteria being claimed |
07-verification.md |
Which criteria have evidence, and the gap list |
06-blast-radius-*.md |
Who and what is exposed |
03b-nfrs.md |
Performance, security, compliance obligations |
06b-change-log.md |
What actually shipped, flags, rollback notes |
runbooks/deploy-*.md |
The deploy and rollback procedure |
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.
- 8d ago First seen · 198 lines · 128 tokens per session scan A 5687352be047
release-readiness is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 21d ago), licensed MIT. It adds 128 tokens to every session and 2,571 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.