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 access-and-onboardinggit 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/access-and-onboarding)<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/access-and-onboarding"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/access-and-onboarding/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/access-and-onboarding"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/access-and-onboarding.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.00141 | $0.02261 |
| Opus 5 | $0.00071 | $0.01130 |
| Sonnet 5 | $0.00028 | $0.00452 |
| Haiku 4.5 | $0.00014 | $0.00226 |
Grade A, and why
access-and-onboarding 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 10d 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.
Access and onboarding
The most reliably underestimated part of an enterprise engagement.
Why this exists
FDEs routinely lose one to two weeks to access. Not because approvals are slow in aggregate, but because they're discovered serially: you request repository access, wait three days, get it, discover you also need the artifact registry, wait four more days, get it, then find the database grant needs a manager's signature and a ticket in a system you don't have an account for.
The lead times aren't the problem. Discovering them one at a time is. Requested in parallel on day one, the same set often lands in under a week.
This skill front-loads the discovery, so the waiting overlaps instead of stacking.
When this applies
- First days at a new organization or on a new system
- Blocked on any permission, credential, or environment
- An engagement is about to widen into systems you don't yet have access to
- You notice you're waiting on something and don't know who to chase
When it doesn't
- You already have everything you need — don't manufacture a register for a one-day task
- The blocker is a person's time rather than a permission. That's
escalation-and-renegotiation.
Prerequisites
.fde/00-engagement.md — the archetype determines what access is actually needed. Without it, you'll request either too much (which slows every approval and makes you look careless with privilege) or too little.
Procedure
1. Enumerate what this engagement needs
Work from the candidate list below. It's deliberately over-inclusive — go through it and mark each needed / not needed / unsure, using the archetype as the filter.
Ask for the least privilege that does the job. Requesting production write access on day one, when read-only would do, slows the approval and tells a security team something about your judgment that you'd rather not tell them.
Foundation
- Network access — VPN, or the office network, or a jump host / VDI
- SSO or directory account, and any MFA enrolment
- Corporate email and chat, plus the specific team channels
- Laptop or VDI itself, with whatever developer entitlement it needs
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.
- 10d ago First seen · 178 lines · 141 tokens per session scan A 800d1c4596f5
access-and-onboarding is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 23d ago), licensed MIT. It adds 141 tokens to every session and 2,261 once invoked, about $0.0007 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.