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 tjdrhs90/rn-launch-harness --skill rn-harness-plangit clone --depth 1 https://github.com/tjdrhs90/rn-launch-harnessWrote 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/tjdrhs90/rn-launch-harness/rn-harness-plan)<a href="https://agentmods.dev/skills/tjdrhs90/rn-launch-harness/rn-harness-plan"><img src="https://agentmods.dev/badge/skills/tjdrhs90/rn-launch-harness/rn-harness-plan/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/tjdrhs90/rn-launch-harness/rn-harness-plan"><img src="https://agentmods.dev/badge/skills/tjdrhs90/rn-launch-harness/rn-harness-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.01478 |
| Opus 5 | $0.00015 | $0.00739 |
| Sonnet 5 | $0.00006 | $0.00296 |
| Haiku 4.5 | $0.00003 | $0.00148 |
Grade A, and why
rn-harness-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 10d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rn-harness-plan — Phase 2: 기획 (PRD)
시장 조사 결과를 기반으로 상세 기획서(PRD)를 작성한다.
Trigger
오케스트레이터에서 Phase 2로 호출됨.
Input
docs/harness/specs/YYYY-MM-DD-research.md(시장 조사)docs/harness/config.mddocs/harness/references/(있으면)
Process
Step 1: 시장 조사 분석
research 산출물을 읽고:
- MVP 기능 리스트 확인
- 차별화 전략 확인
- 기술 타당성 확인
Step 2: PRD 작성
2a. 제품 개요
- 앱 이름 (가안)
- 앱 슬러그 (
app_slug): 앱 이름을 kebab-case 영문으로 변환. Expo 프로젝트 폴더명 + Bundle ID에 사용.- 예: "가계부 앱" →
budget-book, "커피 구독" →coffee-tracker - AskUserQuestion으로 사용자 확인/수정
- 예: "가계부 앱" →
- 한 줄 소개
- 핵심 가치 제안
- 타겟 사용자 페르소나 (2~3개)
2b. 유저 스토리
P0/P1/P2 우선순위로 작성:
US-001 [P0]: 사용자는 이메일로 회원가입할 수 있다.
- 수락 기준: 이메일 형식 검증, 비밀번호 8자 이상, 성공 시 홈 이동
2c. 화면 구조 (Expo Router)
app/
├── _layout.tsx # Root layout
├── (auth)/
│ ├── _layout.tsx
│ ├── login.tsx
│ └── signup.tsx
├── (tabs)/
│ ├── _layout.tsx
│ ├── index.tsx # 홈
│ ├── explore.tsx
│ └── profile.tsx
└── (modal)/
└── settings.tsx
2d. FSD 모듈 맵
src/
├── features/
│ ├── auth/ # 인증
│ ├── home/ # 홈 피드
│ └── profile/ # 프로필
├── entities/
│ ├── user/ # 사용자 도메인
│ └── post/ # 게시물 도메인
├── widgets/
│ └── header/ # 공통 헤더
└── shared/
├── api/ # Axios 클라이언트
├── config/ # 환경설정, 테마
├── lib/ # 유틸리티
├── types/ # 공통 타입
└── ui/ # 공통 컴포넌트
2e. API 설계
POST /auth/login # 로그인
POST /auth/signup # 회원가입
GET /users/:id # 유저 정보
PATCH /users/:id # 유저 수정
GET /posts # 게시물 목록
POST /posts # 게시물 생성
2f. 데이터 모델
주요 엔티티의 필드와 관계 정의.
2g. 광고 배치 전략
AdMob 광고 위치 결정:
- 배너: 탭 하단 또는 리스트 사이
- 전면 광고: 화면 전환 시
- 리워드 광고: 프리미엄 기능 해제
2h. MVP 범위
- 1차 출시 기능 (P0)
- 2차 업데이트 기능 (P1)
- 향후 로드맵 (P2)
Step 3: 사용자 확인
AskUserQuestion으로 PRD 요약 공유:
- 화면 구조 확인
- 핵심 기능 확인
- 광고 배치 확인
- 수정 요청 반영
Output
docs/harness/plans/YYYY-MM-DD-prd.md:
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.
- 10d ago First seen · 199 lines · 29 tokens per session scan A 5a399ae1ec44
rn-harness-plan is a skill published in the GitHub repository tjdrhs90/rn-launch-harness (9 stars, last pushed 9d ago), licensed MIT. It adds 29 tokens to every session and 1,478 once invoked, about $0.0001 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
appstore-publish
A workflow guide for publishing an app to the App Store, including prerequisites, tool loading, submission, and resubmission steps.
playstore-publish
A guide for publishing to Google Play, including required conditions, tool loading, the run sequence, in-app products, and subscriptions. Google Play is Google’s store for Android apps and digital purchases.
app-store-preflight-compliance
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.
ios-marketing-capture
Use when the user wants to automate capture of marketing screenshots for a SwiftUI iOS app across multiple locales, devices, or appearances. Covers full-screen shots, isolated element renders (carousel cards, widgets), and reproducible output naming. Triggers on marketing screenshots, locale screenshots, widget…
implementation-guide
Generates detailed implementation guide with pseudo-code and step-by-step development instructions. Creates IMPLEMENTATIONGUIDE.md from PRD, Architecture, and UX specs. Use when creating development roadmap.
architecture-spec
Generates technical architecture specification from PRD. Covers architecture pattern, tech stack, data models, and app structure. Use when creating ARCHITECTURE.md or designing system architecture.