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 agentmods add rules/epicsagas/velith/velith-pipelinegit clone --depth 1 https://github.com/epicsagas/VelithWrote 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/epicsagas/velith/velith-pipeline)<a href="https://agentmods.dev/rules/epicsagas/velith/velith-pipeline"><img src="https://agentmods.dev/badge/rules/epicsagas/velith/velith-pipeline.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 | $0.01164 | $0.01164 |
| Opus 5 | $0.00582 | $0.00582 |
| Sonnet 5 | $0.00233 | $0.00233 |
| Haiku 4.5 | $0.00116 | $0.00116 |
Grade A, and why
velith-pipeline 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 4d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Velith — AI-Native Book Publishing Pipeline
Overview
Build books like software. 6-phase pipeline from blank page to published book, with quality gates at every stage.
Phase 0: Onboarding → Phase 1: Ideation → Phase 2: Outlining → Phase 3: Drafting → Phase 4: Editing → Phase 5: Publishing
Phase Router
Detect current project state and route to the correct phase:
- No project exists → Phase 0 (Onboarding)
- Project exists, no outline → Phase 1 (Ideation)
- Outline exists, no drafts → Phase 2 (Outlining) validation, then Phase 3
- Drafts exist, incomplete → Phase 3 (Drafting)
- All drafts complete → Phase 4 (Editing)
- Editing complete → Phase 5 (Publishing)
Detection: check for drafts/ directory, outline.md, STYLE.md, PRD.md.
Phase Details
Phase 0: Onboarding
- Genre selection (fiction/non-fiction/technical/screenplay/poetry/game/academic/custom)
- Target audience definition
- Language selection
- Project directory setup
- Source material scan (existing notes, articles, code)
- Generate
STYLE.md(voice, tone, conventions) - Generate
PRD.md(book requirements)
Phase 1: Ideation
- Market research (competing titles, gaps)
- Core concept distillation (elevator pitch)
- Unique value proposition
- Scope definition (chapters, word count, timeline)
- Save to
ideation.md
Phase 2: Outlining
- Generate full chapter outline with dependencies
- Per-chapter specs: title, hook, key concepts, word target, difficulty level
- Cross-chapter reference map
- Save to
outline.md - Agent
book-architectvalidates structure
Phase 3: Drafting
- Plan-Then-Execute: chapter-by-chapter generation
- Each chapter gets: outline context + previous chapter summary + style guide
- Parallel chapter generation (max 4 concurrent)
- Agent
scene-generatordecomposes chapters into scenes (fiction only) - Agent
chapter-writergenerates each chapter - Agent
continuity-editorchecks cross-chapter consistency - Quality gate: line count, frontmatter, style compliance
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.
- 4d ago First seen · 125 lines · 1,164 tokens per session scan A 499adad31e2d
velith-pipeline is a cursor rule published in the GitHub repository epicsagas/Velith (33 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,164 tokens to every session, about $0.0058 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 cursor rules, from other repositories
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-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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.