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-technicalnpx skills add epicsagas/Velith --skill book-technicalgit 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-technical)<a href="https://agentmods.dev/skills/epicsagas/velith/book-technical"><img src="https://agentmods.dev/badge/skills/epicsagas/velith/book-technical.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.00351 |
| Opus 5 | $0.00013 | $0.00176 |
| Sonnet 5 | $0.00005 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
book-technical 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
Technical Book Patterns
Progression: Part1 Intro(15%) → Part2 Foundations(25%) → Part3 Practice(30%) → Part4 Advanced(20%) → Part5 Reference(10%). Novice(what?) → Competent(how?) → Expert(why?).
Chapter: Hook(problem scenario) → Concept(linked to prior) → Code(minimal runnable) → Explanation(line-by-line) → Pitfalls(2-3 beginner mistakes) → Summary + preview.
Code rules: language tag always · runnable only (pseudocode labeled) · include imports · show expected output · filename as title. Beginner: 10-30 lines, Intermediate: 30-80, Advanced: 80-200.
Diagrams: architecture (boxes+arrows), flowchart (Mermaid TD), sequence (Mermaid sequenceDiagram), comparison (markdown table). Pair ASCII + Mermaid for EPUB/PDF compat. ≤3/chapter.
API reference: functionName(params) → one-liner → Parameters table → Returns type → Example code → See also.
Version-independent writing: prefer "Save the file" over "Click File > Save". Exception: security/breaking changes need specific versions.
Labs: objective → prerequisites → steps with verification → result check → challenge. Easy(step-by-step, 3-5), Medium(hints, 5-8), Hard(goal-only, 3-5). Parts 1-2 Easy, Part 3 Medium, Part 4 Hard.
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 · 21 lines · 25 tokens per session scan A bbf767c3c325
book-technical 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 351 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
paper-explainer
科研论文解读：解析 arXiv/PDF 的公式与图表，提炼问题、贡献、方法、关键图和结论，再产出 B站/视频号解读视频或知乎/公众号图文。 当用户说“论文解读、讲论文、论文转视频/图文、科研科普、arXiv、学术视频”时使用。 本 SKILL 从论文做内容；video-to-article 从视频做图文，doc-convert 只转换文档格式。.
yalc-orientation
First-touch onboarding for someone who just opened the YALC repo. Triggers when the user pastes the repo URL https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system (with or without trailing slash, with or without .git), or says any of: 'what is yalc', 'what is this', "let's start", "let's go", 'i just cloned…
intro-example
Minimal MDA source demonstrating relationship-graph footnotes and metadata.mda. MDA-extended fields. Use as a reference fixture when learning the MDA source format.
onboard
Quick onboarding to an existing codebase. Generates a mental model of the architecture, key patterns, and how things connect. Use when joining a new repo or when a teammate needs to get up to speed fast.
learn-anything
This skill should be used when the user wants a beginner-to-expert learning path, curriculum, study plan, or training progression for any topic — academic, physical, creative, linguistic, or professional — built by researching how that domain is optimally taught, then emitting only the first progression tier through a…
capture-learning
Use when a real outcome just landed and the lesson should be banked so the OS stops repeating mistakes - an eval result, a customer reply, a metric move, a failed or won launch, a Share-of-Model move - when the founder says "we just learned", "that worked", "that failed", "log this", "note this for next time"…