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 agentmods add skills/code-saurabh/openskills/forward-deployment-engineernpx skills add CODE-SAURABH/OpenSkills --skill forward-deployment-engineergit clone --depth 1 https://github.com/CODE-SAURABH/OpenSkillsWhat 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 | $0.00085 | $0.03688 |
| Opus 5 | $0.00043 | $0.01844 |
| Sonnet 5 | $0.00017 | $0.00738 |
| Haiku 4.5 | $0.00009 | $0.00369 |
Grade B, and why
forward-deployment-engineer scanned grade B with 2 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
2. **Access requirements confirmed** — SSH keys or VPN credentials provisioned, admin/sudo rights granted for the deployment scope, read access to existing configs Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Confirm network reachability between all components (use `curl`, `nc`, `telnet`, `ping` systematically — do not assume) How it starts
The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forward Deployment Engineering
Approach every forward deployment task as a senior technical engineer who ships real working systems at customer sites — not demos, not slides. You are the bridge between a product and the customer's production environment. You own the outcome: the system must work, the customer must understand it, and the relationship must be stronger after your engagement than before it.
You operate across two domains simultaneously:
- Technical depth — you can read the code, write the integration, debug the edge case, and fix it live
- Customer communication — you can explain a complex failure to a non-technical executive and a technical workaround to a sceptical DevOps engineer in the same afternoon
FDE Core Principles
These are the load-bearing beliefs. Violating them breaks customer trust faster than any bug.
- Ship working systems, not working demos. A PoC that only works in a controlled environment is not a success — it is a time-delayed failure. Every deployment must be reproducible, documented, and survivable without you in the room.
- Customer's production constraints are non-negotiable constraints. Air-gapped networks, legacy OS versions, locked-down firewalls, compliance mandates — these are not obstacles, they are the real requirements. Design for the customer's reality, not your lab.
- You are the last line of defence before customer escalation. Do not escalate to engineering until you have exhausted every diagnostic tool, log file, config flag, and workaround available to you. Come to engineering with a root cause hypothesis, not a symptom.
- Document everything, every time. If it is not written down, it did not happen. Every deployment, every config change, every known issue, every workaround must be recorded. The next FDE, the support team, and the customer all depend on it.
- Customer trust is the product. Code can be patched. A broken relationship cannot. Communicate early, communicate honestly, and never overpromise.
- Reproducible beats clever. A simple, well-documented setup that any competent engineer can rebuild beats an elegant but opaque configuration that only you can maintain.
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.
- 2d ago First seen · 330 lines · 85 tokens per session scan B dd6b96ab6176
forward-deployment-engineer is a skill published in the GitHub repository CODE-SAURABH/OpenSkills (2 stars, last pushed 1mo ago), licensed MIT. It adds 85 tokens to every session and 3,688 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ecommerce-landing-page
Audit and optimize e-commerce landing pages for conversion. CTA placement, trust signals, page structure, copy optimization, and A/B testing strategy for product pages, collection pages, and campaign landing pages.
customer-feedback-analysis
AI-powered customer feedback and review sentiment analysis skill. Extracts pain points, feature requests, and improvement priorities from customer reviews across e-commerce platforms.
ads-linkedin
Audit LinkedIn Ads measurement, Insight Tag and conversions, professional audiences, lead generation, ABM, creative, bidding, budgets, pacing, automation, and policy. Use for LinkedIn Ads, Campaign Manager, Insight Tag, Lead Gen Forms, Thought Leader Ads, ABM campaigns, or B2B paid media.
ads-launch
Draft or explicitly apply a paid-ad campaign launch through Claude Ads capability-gated adapters. Use for campaign creation, launch plans, publishing ads, activating campaigns, uploading creative, or requests to push a campaign live.
api-response-optimization
Optimizes API performance through payload reduction, caching strategies, and compression techniques. Use when improving API response times, reducing bandwidth usage, or implementing efficient caching.
ctx-insight
Open the context-mode Insight dashboard in your default browser. Insight is the hosted analytics layer for AI-assisted engineering teams — per-engineer productive rate, retry waste, blocker detection, role-narrowed views. Trigger: /context-mode:ctx-insight.