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.
git clone --depth 1 https://github.com/ellie1004/fantasy-novel-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/rules/ellie1004/fantasy-novel-harness/novel-workflow)<a href="https://agentmods.dev/rules/ellie1004/fantasy-novel-harness/novel-workflow"><img src="https://agentmods.dev/badge/rules/ellie1004/fantasy-novel-harness/novel-workflow/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/rules/ellie1004/fantasy-novel-harness/novel-workflow"><img src="https://agentmods.dev/badge/rules/ellie1004/fantasy-novel-harness/novel-workflow.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.00000 | $0.00469 |
| Opus 5 | $0.00000 | $0.00234 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
novel-workflow 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.
What it actually says
Fantasy Novel Writing Workflow Rules
필수 준수 사항
- 10단계 순서 준수: 원고분석 → 세계관 → 마법 → 캐릭터 → 음성DNA → 플롯 → 문체 → 집필 → 삽화 → 진단 → 리라이팅 → 베타리더 → 최종빌드
- 설계 문서 선행: 챕터 집필(Step 6) 전에 Step 1~5의 모든 설계 문서가 완료되어야 한다
- 사용자 확인: 각 Step 완료 후 사용자 확인을 받는다 (사용자가 "끝까지 진행해줘" 요청 시 예외)
집필 규칙
- Show, Don't Tell: 감정을 직접 서술하지 말고 행동·대화·감각으로 보여준다
- 장면마다 최소 3가지 감각 묘사 포함 (시각, 청각, 촉각/후각/미각 중 선택)
- 캐릭터 대사는 반드시 voice-dna.md의 음성 DNA를 적용한다
- 삽화 배치 예정 장면은 특히 상세한 시각 묘사를 포함한다
금지 패턴
- "그는 슬펐다" 류의 직접 감정 서술
- "As You Know, Bob" 패턴
- 3문장 이상 연속 설명 블록 (Info-dump)
- 동일 어미 4회 이상 연속 사용
파일 컨벤션
- 설계 문서:
output/design-docs/[문서명].md - 챕터 초안:
output/drafts/chapter-[XX]-draft.md - 챕터 수정본:
output/drafts/chapter-[XX]-revised.md - 삽화:
output/illustrations/chapter-[XX]-scene-[XX].[ext] - 최종본:
output/final/[소설제목]-final.[ext]
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 · 36 lines · 0 tokens per session scan A ebd408426a10
novel-workflow is a cursor rule published in the GitHub repository ellie1004/fantasy-novel-harness (4 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 469 tokens. 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.