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 batterfried-philosophy172/Agent-Startup-Skills --skill mvp-scopergit clone --depth 1 https://github.com/batterfried-philosophy172/Agent-Startup-SkillsWrote 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/batterfried-philosophy172/agent-startup-skills/mvp-scoper)<a href="https://agentmods.dev/skills/batterfried-philosophy172/agent-startup-skills/mvp-scoper"><img src="https://agentmods.dev/badge/skills/batterfried-philosophy172/agent-startup-skills/mvp-scoper/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/batterfried-philosophy172/agent-startup-skills/mvp-scoper"><img src="https://agentmods.dev/badge/skills/batterfried-philosophy172/agent-startup-skills/mvp-scoper.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.00048 | $0.00469 |
| Opus 5.5 | $0.00019 | $0.00188 |
| Sonnet 5.5 | $0.00010 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
mvp-scoper 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 1mo 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.
This is a copy
100% identical to mvp-scoper — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
MVP Scoper — Feature Prioritization Agent
Purpose
Prevent scope creep and feature bloat by ruthlessly prioritizing the smallest set of features that delivers value to the target user.
When to Use
- After market research is approved
- When the user has a long list of desired features
- When the user says "what should I build first?"
Process
Step 1: Dream List
Ask the user to list EVERYTHING they want the product to do. No limits.
Step 2: The Cut
Apply the ICE framework to each feature:
- Impact (1-10): How much does this move the needle for the user?
- Confidence (1-10): How sure are we this is needed?
- Ease (1-10): How easy is this to build?
Score = (Impact × Confidence × Ease). Rank all features.
Step 3: The MVP Line
Draw a hard line at the top 5-7 features. Everything below is "v2 backlog."
Present two lists:
- MVP (v1): The 5-7 features that ship on day one
- Backlog (v2+): Everything else, ranked by ICE score
Step 4: Success Metrics
Define 2-3 measurable success criteria for the MVP:
- e.g., "A new user can complete the core action within 2 minutes"
- e.g., "The app loads in under 3 seconds"
Step 5: Complexity Estimate
For each MVP feature, assign: Low / Medium / High complexity.
Output
Produce a mvp_scope.md file with:
- Prioritized MVP feature list
- v2 backlog
- Success metrics
- Complexity estimates
Exit Criteria
- MVP has no more than 7 features
- Each feature has a clear, one-sentence description
- Success metrics are defined and measurable
- Backlog exists for cut features
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.
- 1mo ago First seen · 62 lines · 48 tokens per session scan A 0cf14d8314b4
mvp-scoper is a skill published in the GitHub repository batterfried-philosophy172/Agent-Startup-Skills (2 stars, last pushed 15d ago), licensed MIT. It adds 48 tokens to every session and 469 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to mvp-scoper, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
craft
Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…
pipeline
Use when the user asks to take a substantial feature from an initial idea through implementation in one mostly autonomous run.
import
Import a self-contained NeatContext context bundle shared by another person, or reconcile a newer copy of a context already on this machine, leaving the source bundle unchanged. Use only when the user explicitly invokes this skill or asks to import a NeatContext bundle.
save
Save durable decisions, findings, plans, and implementation knowledge from the visible Codex conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.
pipeline-auto
Use when the user wants a substantial feature taken from idea through implementation in one run with as little interruption as possible ("just build it", "don't keep asking me"), or when controlling such a run and a worker question, quorum responses, the drift budget, a human decision, a review class or a completeness…
turbo-pipeline
Use when the user wants a feature built end to end after answering one round of questions and then being left alone — "turbo", "ask me once, then just build it", "I'll answer up front, don't come back to me", "decide the rest yourself". Not for a run that wants a spec approval and no tests (superb:fast-pipeline), one…