Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add epicsagas/Velith/plugin install 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-status)<a href="https://agentmods.dev/skills/epicsagas/velith/book-status"><img src="https://agentmods.dev/badge/skills/epicsagas/velith/book-status.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.1 | $0.00035 | $0.00254 |
| Opus 5 | $0.00017 | $0.00127 |
| Sonnet 5 | $0.00007 | $0.00051 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
book-status 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.
What it actually says
Book Status
Run: node ${CLAUDE_PLUGIN_ROOT}/velith.mjs scan [dir] [--ui]
Outputs {dir}/.velith/status.json, updates ~/.velith/velith.db, prints a terminal dashboard including the readiness verdict and score when edits/readiness-report.md exists.
--ui opens the browser dashboard at http://localhost:9631/{index}/overview.
--metrics also runs node ${CLAUDE_PLUGIN_ROOT}/velith.mjs metrics {dir}/drafts and prints per-chapter sentence statistics, repeated phrases, and AI-tell counts. Use it to spot drift between chapters before running the editing pipeline.
Other commands: list (all projects), stats [dir] (JSON), words <file>, snapshot <dir> <label>.
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 Changed · +5 lines · +17 tokens per session a90e61b1e9a6
- 7d ago First seen · 15 lines · 18 tokens per session scan A b20d0bb7dcf3
book-status is a skill published in the GitHub repository epicsagas/Velith (33 stars, last pushed 2d ago), licensed Apache-2.0. It adds 35 tokens to every session and 254 once invoked, about $0.0002 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
kn-handoff
Use when a feature crosses repository boundaries and one side must hand work to the other - generates a self-contained frontend-to-backend brief or backend-to-frontend API contract.
run-execute
Execute work items based on their assigned mode (autopilot, confirm, validate). Supports single-item and multi-item (batch/wide) runs.
status
Display current FIRE project status and validate integrity of intents, work items, and runs.
run-plan
Plan the scope of a run by discovering available work items and suggesting groupings. Invoked before run-execute.
walkthrough-generate
Generate implementation walkthrough for human review after run completion. Documents decisions, changes, and verification steps.
manuscript-manager
Motor de estado. Rastreia tudo entre sessões — capítulos, scores, decisões, handoffs. Sem isso, o contexto se perde e o pipeline desmorona. Usar no INÍCIO e FIM de toda sessão de trabalho no livro. É a peça mais crítica do sistema.