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 skills/epicsagas/velith/book-draftnpx skills add epicsagas/Velith --skill book-draftgit 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/skills/epicsagas/velith/book-draft)<a href="https://agentmods.dev/skills/epicsagas/velith/book-draft"><img src="https://agentmods.dev/badge/skills/epicsagas/velith/book-draft.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.00025 | $0.00271 |
| Opus 5 | $0.00013 | $0.00135 |
| Sonnet 5 | $0.00005 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
book-draft 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.
What it actually says
Phase 3: Drafting
Plan-Then-Execute: pass chapter spec + previous chapter summary + relevant STYLE.md rules + source refs. Omit full prior chapter text, other chapters, full outline.
- Idempotency: skip existing chapters meeting min line count
- Context build: extract spec → prev summary → STYLE rules → source refs
- Write:
ch{NN}-{slug}.mdwith frontmatter (chapter, title, word_target, status, dates) - QA: word count ±10% · frontmatter present · STYLE rules · heading H1→H2→H3 · hook matches spec
Parallel: up to 4 concurrent chapters when prereqs done, no mutual refs.
Continuity (every 3-5 chapters): term consistency, logic flow, character/code compat, reference integrity.
Gate: all chapters exist, ±10% word target, continuity passed.
Post-Completion
Update the project dashboard status:
node {PLUGIN_ROOT}/velith.mjs scan [project-dir] --plugin-root={PLUGIN_ROOT}
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 · 29 lines · 25 tokens per session scan A eba30c491c67
book-draft is a skill published in the GitHub repository epicsagas/Velith (33 stars, last pushed yesterday), licensed Apache-2.0. It adds 25 tokens to every session and 271 once invoked, about $0.0001 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 skills, from other repositories
agent-session-monitor
Real-time agent conversation monitoring - monitors Higress access logs, aggregates conversations by session, tracks token usage. Supports web interface for viewing complete conversation history and costs. Use when users ask about current session token consumption, conversation history, or cost statistics.
higress-daily-report
生成 Higress 项目每日报告，追踪 issue/PR 动态，沉淀问题处理经验，驱动社区问题闭环。用于生成日报、跟进 issue、记录解决方案。.
issue-spec-workflow
Use issue-spec to plan and implement a change through exact-head human review handoff.
open-ontologies
AI-native ontology engineering using 50+ MCP tools backed by an in-memory Oxigraph triple store. Build, validate, query, and govern RDF/OWL ontologies with a generate-validate-iterate loop. Use when building ontologies, knowledge graphs, RDF data, SPARQL queries, BORO/4D modeling, SHACL validation, clinical…
shadcn-ui
Provides complete shadcn/ui component library patterns including installation, configuration, and implementation of accessible React components. Use when setting up shadcn/ui, installing components, building forms with React Hook Form and Zod, customizing themes with Tailwind CSS, or implementing UI patterns like…
debug-trt-mismatch
Use when TensorRT output diverges from a model reference, model-first validation fails, generated text or media is wrong, or a family change introduces a numerical mismatch. Routes the investigation by model modality and escalates from the first divergent boundary to the smallest responsible family-owned operation.