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 commands/lowtidebuild/ebook-writer/generategit clone --depth 1 https://github.com/lowtidebuild/ebook-writerWrote 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/commands/lowtidebuild/ebook-writer/generate)<a href="https://agentmods.dev/commands/lowtidebuild/ebook-writer/generate"><img src="https://agentmods.dev/badge/commands/lowtidebuild/ebook-writer/generate.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.00000 | $0.00681 |
| Opus 5 | $0.00000 | $0.00341 |
| Sonnet 5 | $0.00000 | $0.00136 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
generate 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Ebook
Generate a complete ebook from the given topic.
Usage
/generate <topic> [--plugin <domain>] [--language <ko|en>] [--author <name>] [--bilingual]
Examples
/generate "Claude Code for Lawyers" --plugin legal --author "이기쁨"
/generate "Introduction to Python Programming" --language en --author "John Doe"
/generate "AI 활용 가이드" --bilingual --author "홍길동"
Execution
-
Parse arguments:
- Extract the topic from $ARGUMENTS
- If
--plugin <domain>is specified, verify.claude/plugins/<domain>/PLUGIN.mdexists - If no plugin is specified, do not auto-detect a plugin; run in general-purpose mode
- If plugin directories exist but no
--pluginwas provided, mention them as available options only - For deterministic checks, use
.venv/bin/python3 scripts/plugin_policy.py [--plugin <domain>] - Language detection (in order of priority):
- If
--language <code>is specified, use it - Otherwise, auto-detect from the user's input language:
- Topic in Korean →
primary_language: ko - Topic in English →
primary_language: en
- Topic in Korean →
- If
- If
--author <name>is specified, use as author name- If not specified, ask the user for author name (do NOT default to "Generated by Ebook Writer Agent")
- Bilingual mode:
- If
--bilingualflag is present →bilingual: true - Otherwise, ask the user: "번역본도 함께 만들까요? (Do you also need a translated version?)"
- If yes →
bilingual: true, set secondary_language automatically (ko↔en) - If no →
bilingual: false, skip translation step, produce single-language output only
- If
-
Check for existing pipeline:
- If
output/pipeline_state.jsonexists, offer to resume or restart
- If
-
Initialize new pipeline:
- Create
output/pipeline_state.jsonwith.venv/bin/python3 scripts/pipeline_state.py init - Set
authorfield based on the parsed or user-provided author name - Set
pluginonly when--plugin <domain>was explicitly provided and validated - Set
bilingualfield based on user's choice - Validate the state with
.venv/bin/python3 scripts/pipeline_state.py validate output/pipeline_state.json - Ensure all output subdirectories exist
- Create
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 · 57 lines · 0 tokens per session scan A 270b94b36381
generate is a command 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 681 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.