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 RealDougEubanks/ClaudeMarketplace --skill mvp-readinessgit clone --depth 1 https://github.com/RealDougEubanks/ClaudeMarketplaceWrote 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/realdougeubanks/claudemarketplace/mvp-readiness)<a href="https://agentmods.dev/skills/realdougeubanks/claudemarketplace/mvp-readiness"><img src="https://agentmods.dev/badge/skills/realdougeubanks/claudemarketplace/mvp-readiness/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/realdougeubanks/claudemarketplace/mvp-readiness"><img src="https://agentmods.dev/badge/skills/realdougeubanks/claudemarketplace/mvp-readiness.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.00033 | $0.02364 |
| Opus 5 | $0.00016 | $0.01182 |
| Sonnet 5 | $0.00007 | $0.00473 |
| Haiku 4.5 | $0.00003 | $0.00236 |
Grade A, and why
mvp-readiness scanned grade A with 1 finding 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 11d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Grep for `readFileSync` and `execSync` outside of config-loading or startup modules — flag any found in async request handlers. How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MVP Readiness Audit
Run a structured quality-gate audit before declaring any project an MVP. Check every item. Report pass/fail with evidence. Flag blockers.
Instructions
Two modes:
- Full audit (default
/mvp-readiness): complete checklist across all 8 sections. Use before launch. - Quick scan (
/mvp-readiness --quick): checks only the 5 hard blockers. Completes in under 30 seconds. Use during daily development.
If --quick is passed, skip to the Quick Scan section and stop after producing the quick scan output. Do not run the full checklist.
Quick Scan
Run each of the following 5 checks using Bash or Grep — do not read files individually. Report results in the compact output format below.
Check 1 — Secret Scan
grep -rn "password\s*=\s*['\"]" --include="*.js" --include="*.ts" --include="*.py" --exclude-dir=node_modules .
Adapt the file extensions for the detected language. FAIL if any match is found outside of test files (*.test.*, *.spec.*, tests/, __tests__/).
Check 2 — README Exists
Check that README.md or readme.md exists and is greater than 100 bytes. FAIL if the file is missing or empty.
Check 3 — External Call Error Handling
grep -rn "fetch(\|axios\.\|\.query(\|\.connect(" --include="*.js" --include="*.ts" . | grep -v "try\|catch\|then\|rescue"
This is a rough heuristic. FAIL if more than 5 uncovered calls are found.
Check 4 — No Secrets in Git History
git log --all --oneline -- "*.env" 2>/dev/null | head -5
FAIL if any .env files appear in the git history.
Check 5 — Placeholder Code
grep -rn "TODO\|FIXME\|stub\|placeholder\|impl later" --include="*.js" --include="*.ts" --include="*.py" --exclude-dir=node_modules . | grep -v "test\|spec"
FAIL if any results are found in non-test files.
Quick Scan Output Format
Produce a compact result in this exact format:
## MVP Quick Scan — <project> — <date>
✓ Secret scan: PASSED
✗ README: FAILED — README.md not found
✓ Error handling: PASSED (heuristic)
✓ Git history: PASSED
⚠ Placeholder code: WARNING — 3 TODOs in src/ (non-blocking)
Status: NOT READY — 1 blocker. Run /mvp-readiness for full audit.
What ships with it
4 files 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.
- 11d ago First seen · 200 lines · 33 tokens per session scan A 62b0e742727b
mvp-readiness is a skill published in the GitHub repository RealDougEubanks/ClaudeMarketplace (1 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 2,364 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
tools-unity-test-framework
Unity Test Framework patterns for EditMode and PlayMode tests including async testing, mocking, and test organization.
plan-qa
Post-implementation QA planning — independent of /review (the developer chooses whether to run them sequentially or in parallel), only when the change has a running surface worth driving. Interviews the developer to turn the specs and the diff into an executable QA specification (specs/qa/QA- - .md) that /execute-qa…
execute-qa
Executes a QA specification (specs/qa/QA- - .md) written by /plan-qa: drives every step with the plan's drivers, verifies each Expected line mechanically ([assert]) or by evidence-backed judgment against the plan's written criterion ([judge]), pauses at named operator handoffs, and writes the results artifact…
generate-tasks
Phase 3 of 5 — slices the ARCH doc into verification-ready task specs (tdd/test-after/ui/checklist), emitted as a separate TASKS- - .md file alongside ARCH for the implement skill. Use only when the user asks to run Phase 3 or generate tasks from an ARCH doc — never trigger automatically.
team-qa
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.
smoke-check
Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.