Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add MJbae/awesome-novel-studio/plugin install awesome-novel-studioWrote 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/mjbae/awesome-novel-studio/create)<a href="https://agentmods.dev/skills/mjbae/awesome-novel-studio/create"><img src="https://agentmods.dev/badge/skills/mjbae/awesome-novel-studio/create.svg" alt="Measured on agentmods" 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.00159 | $0.07380 |
| Opus 5 | $0.00079 | $0.03690 |
| Sonnet 5 | $0.00032 | $0.01476 |
| Haiku 4.5 | $0.00016 | $0.00738 |
Grade A, and why
create 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 6d 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 — 476 lines — stays where its author put it; the contents beside it link to each section on GitHub.
에피소드 창작 오케스트레이터
설정문서(캐릭터시트·플롯가이드·부트스트랩)에 따라 에피소드를 순차 창작하는 4-에이전트 파이프라인.
아키텍처
Phase 1 (병렬) Phase 2 (순차) Phase 3 (순차)
┌──────────────────┐ ┌──────────────┐ ┌──────────────┐
│ episode-architect│──┐ │ episode- │ │ quality- │
│ (설계도 추출) │ ├──▶│ creator │──────▶│ verifier │
└──────────────────┘ │ │ (본문 집필) │ │ (7축 검증) │
┌──────────────────┐ │ └──────────────┘ └──────┬───────┘
│ continuity-bridge│──┘ ◀── REWRITE (max 2) ───┘
│ (연속성 수집) │ │
└──────────────────┘ PASS ───▶ 다음 EP
실행 모드: 서브 에이전트 (파이프라인 패턴, lint/revise와 동일)
- 이유: 각 Phase가 이전 Phase 출력에 순차 의존, 에이전트 간 실시간 통신 불필요
전제 조건
- novel-config.md 존재 (프로젝트 디렉토리 내)
- 설정문서 존재: 부트스트랩, 캐릭터시트(core+detail+dialogue DNA), 플롯가이드
- 에피소드 디렉토리 존재 (
episode_dirin novel-config.md)
novel-config.md가 없으면 에러를 출력하고 종료한다.
인자 파싱
| 입력 형태 | 해석 |
|---|---|
/create |
현재 디렉토리에서 novel-config.md 탐색, 마지막 EP 다음부터 |
/create 36억평 |
36억평 프로젝트, 마지막 EP 다음부터 |
/create EP051 |
현재 프로젝트, EP051만 |
/create 36억평 EP051 |
36억평 프로젝트, EP051만 |
/create 36억평 EP051-EP060 |
36억평 프로젝트, EP051~EP060 범위 |
실행 흐름
Step 0: 초기화
-
novel-config.md 필수 필드 검증 게이트: novel-config.md를 로드한 직후, 아래 필수 필드가 모두 존재하고 비어있지 않은지 검증한다. 하나라도 누락되면 에러를 출력하고 즉시 종료한다.
필수 필드 체크리스트: - [ ] project.target_platform — 플랫폼명 - [ ] project.episode_dir — 에피소드 저장 디렉토리 - [ ] project.work_dir — 작업 디렉토리 - [ ] project.design_dir — 설계문서 디렉토리 - [ ] 설정문서 매핑.bootstrap — 부트스트랩 경로 (파일 존재 확인) - [ ] 설정문서 매핑.character_core — 캐릭터 핵심 경로 (파일 존재 확인) - [ ] 설정문서 매핑.character_detail — 캐릭터 상세 경로 (파일 존재 확인) - [ ] EP 범위별 플롯 가이드 — 최소 1개 행 존재 (파일 존재 확인)검증 실패 시 출력:
❌ novel-config.md 필수 필드 누락: - {누락 필드 목록} create 스킬을 실행하려면 위 필드를 채워주세요. 템플릿: ${CLAUDE_PLUGIN_ROOT}/skills/polish/references/project-config-template.md
0.5 target_platform 허용 집합 검증 게이트:
- novel-config.md의
project.target_platform은 아래 canonical name 중 하나여야 한다:- 문피아, 네이버시리즈, 카카오페이지, 리디, 조아라, 노벨피아
- create 스킬은 novel-config.md에 저장된 canonical 값만 사용한다. 별칭 정규화나 자동 치환은 수행하지 않는다.
- 비지원 값이면 에러를 출력하고 즉시 종료한다.
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.
- 6d ago First seen · 476 lines · 159 tokens per session scan A e8a9b37ccf63
create is a skill published in the GitHub repository MJbae/awesome-novel-studio (145 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 159 tokens to every session and 7,380 once invoked, about $0.0008 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…