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 mollyretter/forward-deployed-engineer-toolkit --skill mvp-plangit clone --depth 1 https://github.com/mollyretter/forward-deployed-engineer-toolkitWrote 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/mollyretter/forward-deployed-engineer-toolkit/mvp-plan)<a href="https://agentmods.dev/skills/mollyretter/forward-deployed-engineer-toolkit/mvp-plan"><img src="https://agentmods.dev/badge/skills/mollyretter/forward-deployed-engineer-toolkit/mvp-plan.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.00064 | $0.02325 |
| Opus 5 | $0.00032 | $0.01162 |
| Sonnet 5 | $0.00013 | $0.00465 |
| Haiku 4.5 | $0.00006 | $0.00232 |
Grade A, and why
mvp-plan 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 7d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mvp-plan — from locked identity to a scoped, gated MVP plan
When to use
Immediately after north-star locks, before any design-system, mockup, architecture, or build work. Re-run only when the founder explicitly reopens scope (same one-way ratchet as north-star's drift rule).
Skip for: products without a locked north star (run north-star first — this skill refuses to proceed without docs/00-north-star.md), features on an existing product, pure technical decisions.
What it produces
<project>/docs/002-mvp-plan.md— the MVP plan, whose spine is a CHECKLIST from idea to launch: every step as a checkbox — finalize features, market research, design guidance, actual design and screenshot approvals, architecture, build, money, launch — including steps already done at writing time (listed unchecked with a done-date annotation; the founder checks them off themselves when they review the list in the repo). Around the checklist: riskiest assumption, MVP scope in/out, success metrics and kill criteria in the founder's numbers, open-decisions table. Numbered-doc convention is inherited from the reference project — confirm the next free number in the target project'sdocs/folder rather than assuming002verbatim (the reference project reserved001for a still-undetermined doc between north-star and mvp-plan).<project>/docs/build-logs/mvp-plan-v{N}.md— session record: founder's verbatim answers, draft evolution with rejection reasons, review findings and items acted on.- Counter increment in
<project>/docs/eval-runs/mvp-plan.md(runs_total, andruns_surgerywhen Phase 1 detects surgery mode — mirrors north-star'sruns_total/runs_driftsplit).
Hard rules
- A locked north star is a precondition. Read
docs/00-north-star.mdand the north-star build log's positioning context before the first question. Ifdocs/00-north-star.mdis missing, stop and say so. (North-star has no on-disk unlocked/draft state — the file's presence means it's locked.) - The plan stays DRAFT until the founder flips it. Writing the document is not approval. The header says DRAFT and names the founder as the only one who changes that. Never mark it approved yourself.
- Success metrics and kill criteria are the founder's numbers. The skill may cite research-derived calibration ranges (with source) anywhere in the plan. It NEVER invents the founder's specific commit numbers for the success-metrics/kill-criteria section; those ship as labeled blanks until the founder gives them — blanks are honest, invented numbers are not.
- Kill criteria are written while emotionally neutral — before build, before sunk cost. Present this as the reason the question is asked now, not later.
- Founder's verbatim language in the build log. Same as north-star: quotes are quotes, summaries are marked as summaries. Ask consent before recording sensitive disclosures, and before fixing spelling in quoted text.
- No old rulings carried silently. Decisions from prior plans or superseded products enter as inputs to re-decide at a named phase, never as standing authority.
- Review findings are triaged by the founder, never auto-applied. Present a concise punch list; apply only what the founder picks.
- Cross-model review at lock is required — a fan-out (Sonnet + Opus + Haiku) on the final draft with a must-fix-only mandate ("SHIP or FIX, don't relitigate settled style"); cap the punch list at 3 only when reviewers converge on 3 or fewer — surface all consensus must-fix items if there are more. Mid-flight single-model reviews are optional and founder-triggerable at any point.
- Every phase gate in the plan opens with a plain-language brief and the founder's explicit yes. The plan encodes this; the skill models it in miniature by not handing off the draft until the founder has confirmed in chat that v1 reads right (Phase 4) — that confirmation is not the DRAFT-to-approved flip, which stays the founder's separate later act per Hard rule 2.
- The founder edits the file directly once a draft exists. Iterate v1 conversationally; then open
docs/002-mvp-plan.mdin their editor and hand it over.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 89 lines · 64 tokens per session scan A 19d1f9fa7eab
mvp-plan is a skill published in the GitHub repository mollyretter/forward-deployed-engineer-toolkit (9 stars, last pushed 16d ago), licensed MIT. It adds 64 tokens to every session and 2,325 once invoked, about $0.0003 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
fde
Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Use when they prep a…
simple-tasks
Install a fast local task workflow for single-project planning with scripts/task.sh (claim, done, status, reporting) backed by tasks/TASKS.md and optional tasks/details/ notes. Use for lightweight in-progress task coordination, not full team issue tracking.
ship-roadmap
Found or continue a roadmap autopilot one stage per invocation. Default: human merge. --fullauto is invocation-scoped and uses the transient wrapper only after a fresh audit. Triggers: "ship-roadmap", "ship the roadmap", "autopilot this project".
workflow-status
Read-only workflow sensor: compute repository, roadmap, dependency, PR, finding, and recovery state, then emit the fixed machine envelope. Never edits. Triggers: "workflow-status", "workflow status", "what can I build next", "state of the run".
review-spec
Independent read-only review of a frozen Product half before engineering planning. Runs the exact Product checks in a clean context and returns only SPEC-REVIEW-PASS, SPEC-REVIEW-FAIL, or NEEDS-DESIGN with a content-bound receipt. Never edits the reviewed SPEC. Triggers: "review-spec", "review the spec", "review…
tasknotes
Manage tasks in an Obsidian TaskNotes vault. Use for creating, reading, updating, or completing tasks; checking what is open or in progress; adding items to a list; marking tasks done or in progress; updating task status or priority; investigating why a task is missing from a view or board; troubleshooting TaskNotes…