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 rungchan2/frontend-skills --skill mvp-roadmapgit clone --depth 1 https://github.com/rungchan2/frontend-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/rungchan2/frontend-skills/mvp-roadmap)<a href="https://agentmods.dev/skills/rungchan2/frontend-skills/mvp-roadmap"><img src="https://agentmods.dev/badge/skills/rungchan2/frontend-skills/mvp-roadmap/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/rungchan2/frontend-skills/mvp-roadmap"><img src="https://agentmods.dev/badge/skills/rungchan2/frontend-skills/mvp-roadmap.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.00075 | $0.01975 |
| Opus 5 | $0.00037 | $0.00988 |
| Sonnet 5 | $0.00015 | $0.00395 |
| Haiku 4.5 | $0.00007 | $0.00198 |
Grade A, and why
mvp-roadmap 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MVP Roadmap Generator
개발 순서와 일정을 정의하는 MVP Roadmap 문서 생성 가이드.
워크플로우
1. 인터뷰 → 2. 복잡도 추정 → 3. 의존성 분석 → 4. 문서 생성 → 5. 검토/보완
레퍼런스 파일
| 파일 | 용도 | 언제 참조 |
|---|---|---|
references/complexity-guide.md |
기능 타입별 복잡도/소요시간 기준 | 복잡도 추정 시 |
references/mermaid-templates.md |
의존성 다이어그램 템플릿 | 의존성 시각화 시 |
복잡도 기준 요약
| 복잡도 | 프론트 | 백엔드 | 풀스택 |
|---|---|---|---|
| S | 1일 | 1일 | 2일 |
| M | 2-3일 | 2-3일 | 4-5일 |
| L | 1주 | 1주 | 1.5-2주 |
| XL | 2주+ | 2주+ | 3주+ |
상세 기준은 references/complexity-guide.md 참조.
인터뷰 질문
순차적으로 질문하여 정보 수집. 한 번에 2-3개씩 질문.
필수 질문
일정
- "출시 목표 일정은?"
- "개발 리소스는? (인원/시간)"
우선순위
- "가장 먼저 출시하고 싶은 기능은?"
- "꼭 1차에 들어가야 하는 기능 vs 나중에 해도 되는 기능?"
리스크
- "예상되는 기술적 도전은?"
- "외부 의존성이 있나요? (API, 결제 등)"
선택 질문 (필요시)
- "스프린트 주기는? (1주/2주)"
- "QA 프로세스가 있나요?"
- "배포 주기는?"
MVP Roadmap 템플릿
# MVP Roadmap: [서비스명]
## 1. 프로젝트 개요
- **출시 목표**: YYYY-MM-DD
- **개발 인원**: N명
- **스프린트 주기**: 2주
## 2. 마일스톤 정의
| ID | 이름 | 기간 | 목표 | 성공 기준 |
|----|------|------|------|----------|
| M1 | Alpha | 4-6주 | 핵심 기능 동작 | 주요 플로우 완성 |
| M2 | Beta | 4-6주 | 테스트 가능 | 전체 기능 완성 |
| M3 | Release | 2-4주 | 출시 준비 | 버그 수정, 최적화 |
## 3. 의존성 다이어그램
```mermaid
graph LR
subgraph M1["M1: Alpha"]
T001[프로젝트 설정]
F001[인증]
F002[핵심 기능]
end
subgraph M2["M2: Beta"]
F003[확장 기능]
F004[검색]
end
T001 --> F001
F001 --> F002
F002 --> F003
F003 --> F004
4. 기능 분해 (Feature Breakdown)
F001: 회원가입/로그인
- 마일스톤: M1
- 우선순위: P0
- 복잡도: M
- 예상 소요: 4일
| ID | 태스크 | 타입 | 시간 | 의존성 |
|---|---|---|---|---|
| F001-1 | 회원가입 API | backend | 1일 | T001 |
| F001-2 | 로그인 API | backend | 0.5일 | F001-1 |
| F001-3 | 회원가입 UI | frontend | 1일 | F001-1 |
| F001-4 | 로그인 UI | frontend | 0.5일 | F001-2 |
| F001-5 | 인증 상태관리 | frontend | 1일 | F001-4 |
수용 기준:
- 이메일/비밀번호로 회원가입 가능
- 로그인 후 인증 상태 유지
- 유효성 검증 및 에러 처리
F002: [기능명]
(동일 구조 반복)
5. 인프라 태스크
| ID | 이름 | 마일스톤 | 복잡도 | 소요 |
|---|---|---|---|---|
| T001 | 프로젝트 설정 | M1 | S | 1일 |
| T002 | CI/CD 구축 | M1 | M | 2일 |
| T003 | 모니터링 설정 | M3 | M | 2일 |
6. 스프린트 계획
Sprint 1 (Week 1-2)
- 목표: 프로젝트 설정 및 인증 시스템
- 용량: 10일 (2명 × 5일)
| 태스크 | 담당 | 예상 | 상태 |
|---|---|---|---|
| T001 | Dev1 | 1일 | |
| T002 | Dev1 | 2일 | |
| F001-1 | Dev2 | 1일 | |
| F001-2 | Dev2 | 0.5일 | |
| F001-3 | Dev1 | 1일 | |
| F001-4 | Dev1 | 0.5일 | |
| F001-5 | Dev2 | 1일 |
버퍼: 2일 (20%)
Sprint 2 (Week 3-4)
(동일 구조)
7. 외부 의존성
| 기능 | 의존 대상 | 타입 | 예상 소요 | Blocking |
|---|---|---|---|---|
| F007 | Stripe 계약 | External | 1주 | Yes |
| F003 | 디자인 확정 | Internal | - | Soft |
8. 리스크 관리
| ID | 리스크 | 확률 | 영향 | 대응 방안 |
|---|---|---|---|---|
| R001 | PG 연동 지연 | Medium | High | 테스트 모드로 먼저 개발 |
| R002 | 요구사항 변경 | High | Medium | 버퍼 확보, 주간 싱크 |
9. 체크리스트 (기능별)
공통
- API 스펙 정의
- DB 스키마 설계
- 컴포넌트 구현
- API 연동
- 에러 핸들링
- 로딩 상태
- 테스트 작성
What ships with it
3 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.
- 12d ago First seen · 231 lines · 75 tokens per session scan A 6ae91f9cb2af
mvp-roadmap is a skill published in the GitHub repository rungchan2/frontend-skills (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 75 tokens to every session and 1,975 once invoked, about $0.0004 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.