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-genresgit 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-genres)<a href="https://agentmods.dev/rules/epicsagas/velith/velith-genres"><img src="https://agentmods.dev/badge/rules/epicsagas/velith/velith-genres.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.00000 | $0.00584 |
| Opus 5 | $0.00000 | $0.00292 |
| Sonnet 5 | $0.00000 | $0.00117 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
velith-genres 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Velith — Genre Conventions
Fiction
- Plot structure: Save the Cat! 15-beat or Snowflake Method
- Character bible with GMC (Goal, Motivation, Conflict) per character
- Scene beats with RDD (Reaction, Dilemma, Decision) pacing
- POV consistency (no 1st/3rd mixing within chapters)
- Dialogue rules: subtext over exposition, distinctive voice per character
Non-Fiction
- Problem-solution structure per chapter
- Learner persona–driven progression (what does the reader already know?)
- Evidence hierarchy: primary research > expert interviews > case studies > anecdotes
- Chapter hooks: open with a question or counterintuitive fact
- Summary + action items at chapter end
Technical
- Concept progression gradient: novice → intermediate → expert
- Code examples: compilable, commented, with expected output
- Diagrams for architecture, data flow, or process steps
- API docs: endpoint, parameters, response schema, error codes
- Labs/exercises at end of each chapter
Screenplay
- 3-act structure + 8-sequence method
- Dialogue: subtext, distinct voice, no on-the-nose exposition
- A/B story interweaving (main plot + subplot)
- Action lines: present tense, visual, concise
- Page budget: ~1 page = ~1 minute of screen time
Poetry
- Form types: sonnet, haiku, free verse, villanelle, prose poem, etc.
- Meter/rhythm awareness (iambic, trochaic, anapestic, dactylic)
- Imagery systems: visual, auditory, tactile, olfactory, gustatory
- Collection arc: ordering poems for emotional/thematic progression
- Line break intentionality: enjambment vs end-stopped
Game Scenario
- Quest/event tree structure with branching conditions
- Dialogue branching with player agency flags
- Lore bible: world rules, factions, technology/magic systems
- Flag system: track player choices across chapters/scenes
- Multiple endings: foreshadowing and divergence points
Academic
- IMRAD structure (Introduction, Methods, Results, Discussion)
- Literature review: thematic organization, not chronological
- Argument chains: claim → evidence → warrant → backing → rebuttal
- Citation practices: consistent style (APA, MLA, Chicago, etc.)
- Abstract and keywords before main body
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 · 65 lines · 0 tokens per session scan A 73d66a2906ae
velith-genres is a cursor rule published in the GitHub repository epicsagas/Velith (33 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 584 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-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.