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-editinggit clone --depth 1 https://github.com/epicsagas/VelithWhat 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.00651 |
| Opus 5 | $0.00000 | $0.00326 |
| Sonnet 5 | $0.00000 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
velith-editing 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 2d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Velith — Editing Pipeline and Style Conventions
5-Stage Editing Pipeline
| Stage | Focus | What to check |
|---|---|---|
| 1. Editorial Assessment | Macro structure | Chapter order, pacing, gap analysis, argument flow |
| 2. Developmental Edit | Flow and content | Transitions, evidence quality, redundant sections, missing content |
| 3. Line Edit | Sentence-level clarity | Word choice, sentence rhythm, paragraph flow, voice consistency |
| 4. Copy Edit | Grammar and consistency | Grammar, punctuation, terminology consistency, formatting |
| 5. Proofread | Final polish | Typos, spacing, formatting artifacts, cross-reference accuracy |
AI-Slop Detection Patterns
These patterns indicate AI-generated text that reads as inauthentic. Flag and fix:
Excessive modifiers: revolutionary, game-changer, groundbreaking, cutting-edge, transformative, innovative, seamless, robust, comprehensive
Repetitive transitions: overuse of "however", "moreover", "furthermore", "additionally", "notably"
Generic conclusions: "in conclusion", "in summary", "ultimately", "at the end of the day", "it's important to note"
Weak hedging: "can be", "seems like", "it could be argued", "one might say", "arguably"
English AI markers: "delve", "tapestry", "landscape" (metaphorical), "nuanced", "multifaceted", "plethora", "myriad"
List overuse: 5+ consecutive bullet points without prose context
Style Drift Indicators
Quantitative signals that a chapter's style has drifted from the rest:
- Sentence length variance — compare per-chapter average against book mean
- Paragraph length distribution — flag chapters with significantly different patterns
- Type-token ratio — vocabulary diversity should remain consistent
- POV mixing — detect shifts between 1st/3rd person within chapters
Severity Classification
| Level | Criteria | Action |
|---|---|---|
| Critical | Breaks reader comprehension, factual error, POV violation | Must fix before proceeding |
| Major | Style drift, inconsistent tone, structural gap | Should fix, flag for review |
| Minor | Word choice, transition quality, formatting | Nice to fix, batch at proofread stage |
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.
- 2d ago First seen · 69 lines · 0 tokens per session scan A 9e593e35475f
velith-editing is a cursor rule published in the GitHub repository epicsagas/Velith (33 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 651 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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.