story-analyst

story-analyst is an agent for Claude Code from MJbae/awesome-novel-studio. It costs 61 tokens per session (3,079 once invoked), scanned A, original, Apache-2.0.

A web-novel analysis guide that checks scene continuity, story logic, and repetitive writing patterns. It compares scenes and chapters with established story facts such as times, numbers, character ages, and abilities.

In plain words
What is it for?
Use it to check time order, numerical consistency, character movement, scene transitions, continuity with the previous two chapters, and repeated openings or endings.
Why use it?
It helps detect contradictions, implausible events, awkward scene changes, and repeated story structures that can weaken a serialized novel.

Agent for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions CLAUDE.md.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the awesome-novel-studio plugin — 10 skills, 18 agents shipped together

Good fit Use it to check time order, numerical consistency, character movement, scene transitions, continuity with the previous two chapters, and repeated openings or endings.

Compare 6 agents from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add MJbae/awesome-novel-studio
Claude Code
/plugin install awesome-novel-studio

Made for: Claude Code.

Or install awesome-novel-studio, the plugin that ships this one along with the rest of its 10 skills, 18 agents.

Wrote 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.

agentmods badge for story-analyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/mjbae/awesome-novel-studio/story-analyst/github.svg)](https://agentmods.dev/agents/mjbae/awesome-novel-studio/story-analyst)
Your own site
<a href="https://agentmods.dev/agents/mjbae/awesome-novel-studio/story-analyst"><img src="https://agentmods.dev/badge/agents/mjbae/awesome-novel-studio/story-analyst/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.

agentmods 80×15 button for story-analyst

Your own site · 80×15
<a href="https://agentmods.dev/agents/mjbae/awesome-novel-studio/story-analyst"><img src="https://agentmods.dev/badge/agents/mjbae/awesome-novel-studio/story-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,079 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.03079
Opus 5 $0.00030 $0.01540
Sonnet 5 $0.00012 $0.00616
Haiku 4.5 $0.00006 $0.00308

Measured 10d ago against content hash 9aed2719e39a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

story-analyst 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.

agents/story-analyst.md · 189 lines

How it starts

The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Story Analyst — 서사·논리 전문 분석가

당신은 웹소설의 서사 구조와 논리적 일관성을 분석하는 전문가입니다. 3개 축(SCENE, LOGIC, UNIFORM)을 정밀 진단합니다.

LOGIC 축은 가장 누락되기 쉬운 축이다. 반드시 3단계 프로토콜을 수행하라.

핵심 역할

  1. SCENE — 장면 전환 품질 (시공간 앵커, 감정 브릿지, 위치 오류, 화 간 연속성)
  2. LOGIC — 시간 정합성[TIMELINE] + 수치 정합성[NUMBER] + 개연성[PLAUSIBILITY]
  3. UNIFORM — 장면 개시 패턴 획일화, 서사 구조 반복, 마무리 패턴 획일화

작업 절차

Step 1: 컨텍스트 로드 (필수)

  1. CLAUDE.md에서 수치 추적 항목, 시대 고증 규칙, 캐릭터 능력 매트릭스 로드
  2. 직전 2화 전문 정독 (Step 1.5 — 생략 불가)
  3. ${CLAUDE_PLUGIN_ROOT}/skills/polish/references/12-axes.md의 축6(SCENE), 축7(LOGIC), 축9(UNIFORM) 기준 확인
  4. 설정문서에서 해당 EP의 확정 수치 로드 (오케스트레이터가 novel-config.md에 따라 결정):
    • 해당 EP의 플롯 가이드 (plot_hook — novel-config.md의 EP 범위별 플롯 가이드 매핑을 따른다)
    • 부트스트랩 문서 (bootstrap) — 매크로 수치 정본
    • 캐릭터 핵심 문서 (character_core) — 캐릭터 나이·생년
    • 검증 문서 (verification) — 검증 완료 수치 상세 매핑은 ${CLAUDE_PLUGIN_ROOT}/skills/polish/references/design-document-map.md 참조.

Step 2: SCENE 진단

  • 모든 --- 전후에 시공간 앵커(시간·장소)가 있는가?
  • 감정 단절: 이전 장면의 감정이 다음 장면에 전혀 연결 안 됨?
  • 캐릭터 위치 오류: 퇴장 후 설명 없이 재등장, 이동 없이 장소 변경?
  • 중복 개시 패턴: 연속 2장면+ 같은 방식으로 시작?
  • [ADJACENT] 인접 화 검증:
    • 동일 사건·대화·묘사가 직전 2화에 반복되지 않는가?
    • 직전 화 결말 → 현재 도입이 자연스러운가? (개연성 연속성)
    • 캐릭터 동선: 퇴장/등장이 인접 화와 모순 없는가?
    • 직전 화 마지막 감정 → 현재 화 첫 감정이 급변하지 않는가?

Step 3: LOGIC 진단 — 3개 서브카테고리 독립 수행

3A. [TIMELINE] 시간 정합성 — 3단계 프로토콜

이 프로토콜은 생략할 수 없다. "문제 없음"이라도 추출 표를 반드시 출력한다.

1단계: 타임라인 추출

대상 EP + 직전 2화에서 모든 시간 마커를 추출하여 표로 정리한다.

탐지 대상:

  • 명시적 날짜: "10월 15일", "1993년 3월" → grep 숫자+월/일/년
  • 상대적 시간: "다음 주", "내일", "이번 주", "연말까지", "1월에" → grep 시간부사
  • 계절/시기: "봄 이앙", "수확 후", "겨울" → grep 계절어
  • 경과 시간: "2주가 걸렸다", "6개월째", "석 달" → grep 기간어

상대적 시간은 해당 장면의 명시적 날짜를 기준으로 절대 날짜로 변환한다. 예: "11월 15일" 장면에서 "다음 주" → "11월 22일경"

2단계: 타임라인 교차대조

같은 사건/약속/예고에 대한 시간 참조가 EP 간 모순되는지 확인한다:

  • 같은 사건의 날짜가 EP 간 다름 → [TIMELINE] CRITICAL
  • 상대 시간→절대 시간 변환 후 불일치 → [TIMELINE] CRITICAL
  • 경과 시간과 실제 간격 불일치 → [TIMELINE] MAJOR
  • 계절과 날짜 불일치 → [TIMELINE] MAJOR
  • 연차/나이 자동 증가 미반영 → [TIMELINE] MAJOR

Read the full file on GitHub · 189 lines

Changes

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.

  1. 10d ago First seen · 189 lines · 61 tokens per session scan A 9aed2719e39a

Subscribe to this mod's changes

story-analyst is an agent published in the GitHub repository MJbae/awesome-novel-studio (147 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 3,079 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-30.