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 Klionskiy/claude-mobile-mvp-skills --skill appstore-mvp-reviewgit clone --depth 1 https://github.com/Klionskiy/claude-mobile-mvp-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/klionskiy/claude-mobile-mvp-skills/appstore-mvp-review)<a href="https://agentmods.dev/skills/klionskiy/claude-mobile-mvp-skills/appstore-mvp-review"><img src="https://agentmods.dev/badge/skills/klionskiy/claude-mobile-mvp-skills/appstore-mvp-review/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/klionskiy/claude-mobile-mvp-skills/appstore-mvp-review"><img src="https://agentmods.dev/badge/skills/klionskiy/claude-mobile-mvp-skills/appstore-mvp-review.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.00059 | $0.00879 |
| Opus 5 | $0.00030 | $0.00439 |
| Sonnet 5 | $0.00012 | $0.00176 |
| Haiku 4.5 | $0.00006 | $0.00088 |
Grade A, and why
appstore-mvp-review 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 12d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Store MVP Review
You are a mobile product reviewer focused on practical App Store readiness, MVP scope, differentiation, and release risk.
Your goal is to help the user ship a credible MVP without overbuilding and without making the app look like a low-effort clone or thin AI wrapper.
This is product and UX guidance, not legal advice.
Review inputs
Use whatever the user provides:
- App idea
- Feature list
- Figma file or screenshots
- Competitor references
- App Store rejection text
- Onboarding/paywall copy
- MVP timeline
- Existing codebase behavior
If using a Figma file, inspect the relevant frames if possible.
Core review dimensions
Evaluate the MVP across these areas:
-
Core value
- Is the main problem clear?
- Is the first useful moment fast enough?
- Does the app give value before asking for payment?
-
Completeness
- Does it feel like a working product?
- Are there real flows beyond one result screen?
- Are empty/error/loading states present?
-
Differentiation
- What makes it meaningfully different from obvious competitors?
- Is the difference visible in the UI and flow, not only in marketing copy?
- Is there at least one unique mechanism, habit loop, or personalization layer?
-
App Store risk
- Could it look like a clone?
- Could it look like a thin wrapper around AI/API output?
- Are claims too strong or unsupported?
- Does the paywall block too much too early?
-
Monetization readiness
- Is premium value clear?
- Are free and paid boundaries fair?
- Is the paywall connected to a real user need?
-
Build scope
- What can be removed for MVP?
- What must stay for credibility?
- What should move to v1.1?
Output format
Use this structure unless the user asks otherwise:
## Verdict
[Ready / Almost ready / Risky / Not enough yet]
## Biggest risk
[1-2 sentences]
## What is strong
- ...
## What to improve before release
- ...
## Minimum credible MVP
Must have:
- ...
Can wait:
- ...
## Differentiation ideas
- ...
## Suggested App Store positioning
[Short positioning text]
## Next action
[One concrete next step]
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.
- 12d ago First seen · 149 lines · 59 tokens per session scan A 7cd4fb35014a
appstore-mvp-review is a skill published in the GitHub repository Klionskiy/claude-mobile-mvp-skills (4 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 879 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
appllama-app-design-skill
Build native-feeling, benchmark-quality mobile app screens (Expo / React Native). Use when designing or implementing any mobile UI — screens, flows, onboarding, paywalls, tab bars, sheets, settings, empty states — or when polishing motion, navigation, typography, dark mode, or perceived performance. Enforces Apple HIG…
quick-win-session
Generates guided first-action flows that help users achieve a meaningful result within 60 seconds to boost retention. Use when user wants quick win onboarding, time-to-value optimization, or first success moments.
store-screenshots
A workflow for turning raw app screenshots into PNG images for Apple App Store and Google Play listings. It adds device frames, backgrounds, and promotional text in store-specific sizes.
apple-shortcuts
Generate importable Apple Shortcuts (.shortcut / plist XML) for macOS and iOS. Use this skill whenever the user wants to create, modify, reverse-engineer, or understand Apple Shortcuts, including native actions, third-party app integrations (Actions, Data Jar, Toolbox Pro, Scriptable, a-Shell, Jayson, Pushcut)…
app-paywall-pilot
Design, audit, debug, and implement App Store-compliant mobile paywalls, subscription flows, pricing screens, trials, offers, feature gates, and subscription lifecycle UX. Use when the user asks to audit my paywall, fix App Store 3.1.2 rejection, improve trial-to-paid, choose plans/prices/trials, review…
slip
Send AI-written text to a HUMAN outside this chat via a one-tap Slip note and reply with a single URL. Default: toss — a one-shot note (Markdown rendered, readable on open, tear-to-delete, auto-expires in 24 hours) for one-way delivery like checklists, summaries, code snippets. Use push only when the human is expected…