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 post-deploy-watchgit 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/post-deploy-watch)<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/post-deploy-watch"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/post-deploy-watch.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.00106 | $0.01948 |
| Opus 5 | $0.00053 | $0.00974 |
| Sonnet 5 | $0.00021 | $0.00390 |
| Haiku 4.5 | $0.00011 | $0.00195 |
Grade A, and why
post-deploy-watch 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-deploy watch
The part after the pipeline goes green.
Why this exists
Deployment is treated as complete when the pipeline succeeds. That's the moment the change starts being tested by reality, not the moment it finishes.
Two specific failures follow from stopping there. The first: nobody watches, the change degrades something subtly, and it's found days later by a customer or a month-end report — by which point the connection to the deploy is lost and diagnosis starts from scratch. The second: someone does watch, sees nothing alarming, and declares it fine — which is a feeling, not a verification, and it's indistinguishable from not having watched.
This skill exists to close the loop that release-readiness opened. Every item accepted as residual risk was accepted on the understanding that it would be detectable. This is where that promise is kept.
When this applies
- Immediately after any non-routine deploy
- During a staged or percentage rollout
- A change shipped with accepted residual risk
- The first production run of anything new
When it doesn't
- Routine low-risk deploys in a mature pipeline with good alerting
- Something has already broken — that's
incident-triage - Non-production environments
Prerequisites
- Locate the workspace:
FDE_WORKSPACE, else the charter Location, else.fde/, else../<repo>-fde/ .fde/08-release-readiness.md— the residual unknowns are your watch list.fde/runbooks/deploy-*.md— rollback triggers and procedure.fde/03b-nfrs.md— the targets you're watching against
Procedure
1. Derive the watch list from the residual unknowns
The connection that makes this skill work. release-readiness produced a list of things that were unverified but accepted because they were judged detectable. Each one is a watch item, and the watch is where "detectable" gets tested.
For each: what specifically would you see if the pessimistic case is true, and where would you see it?
Add the standard set: error rate, latency, throughput, and the specific business metric this change touches.
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 · 167 lines · 106 tokens per session scan A a97ea381dc2d
post-deploy-watch is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 21d ago), licensed MIT. It adds 106 tokens to every session and 1,948 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.