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/lowtidebuild/ebook-writer/code-example-validatornpx skills add lowtidebuild/ebook-writer --skill code-example-validatorgit clone --depth 1 https://github.com/lowtidebuild/ebook-writerWhat 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.00497 |
| Opus 5 | $0.00000 | $0.00249 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
code-example-validator scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Runnable blocks with obvious network usage (`requests`, `urllib`, `socket`, `http.client`, `curl`, `wget`, `nc`, `ssh`) fail before execution How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Example Validator Skill
Purpose
Validate code examples embedded in chapter markdown files, including syntax-only checks and opt-in execution for :runnable blocks.
Capabilities
- Extract fenced code blocks from markdown files
- Validate syntax per language (Python, JavaScript, Bash, etc.)
- Execute trusted
:runnableexamples in a sandbox backend - Report validation results as JSON
Scripts
scripts/validate_code.py— Extract and validate code blocks from a markdown file
Usage
.venv/bin/python3 .claude/skills/code-example-validator/scripts/validate_code.py <markdown_file>
.venv/bin/python3 .claude/skills/code-example-validator/scripts/validate_code.py --execute --sandbox auto output/chapters/ko/
.venv/bin/python3 .claude/skills/code-example-validator/scripts/validate_code.py --execute --sandbox process --allow-unsafe-process output/chapters/ko/
Output: JSON to stdout
{
"file": "ch01_introduction.md",
"total_blocks": 5,
"valid": 4,
"invalid": 1,
"errors": [
{
"block_index": 3,
"language": "python",
"line_in_file": 45,
"error": "SyntaxError: unexpected EOF while parsing"
}
]
}
When to Use
- Writer Agent after completing a chapter (Step 3)
- Editor Agent during validation (Step 4)
Supported Languages
- Python:
ast.parse()validation - JavaScript:
node --checkif available - Bash/Shell:
bash -nsyntax check - Other languages: skip validation, report as "unchecked"
Failure Handling
- If a language validator is not available (e.g., node not installed): skip, mark as "unchecked"
- Never fail the entire validation because of one unsupported language
--execute --sandbox autoprefers Docker isolation (--network none, read-only rootfs, tmpfs workspace)- Process execution requires
--allow-unsafe-processand is for trusted local examples only - Runnable blocks with obvious network usage (
requests,urllib,socket,http.client,curl,wget,nc,ssh) fail before execution
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 56 lines · 0 tokens per session scan A d2f39fc90b7e
code-example-validator is a skill published in the GitHub repository lowtidebuild/ebook-writer (5 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 497 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…