init

A setup command that creates the standard files and folders for a new Bookwright technical non-fiction project.

In plain words
What is it for?
Use it to start a prose-only, Python, R, or Quarto book project and record the selected notebook tools and project conventions.
Why use it?
It gives the project a consistent structure for LaTeX chapters, notebooks, source papers, specifications, plans, references, and build instructions.

Command

Install

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.

agentmods
npx agentmods add commands/queelius/claude-anvil/init
Clone the repo
git clone --depth 1 https://github.com/queelius/claude-anvil
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 596 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.00596
Opus 5 $0.00012 $0.00298
Sonnet 5 $0.00005 $0.00119
Haiku 4.5 $0.00002 $0.00060

Measured 2d ago against content hash a573a0d124df, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

init 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.

bookwright/commands/init.md · 35 lines

How it starts

The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/bookwright:init

Scaffold a fresh book project at the current working directory (or a named subdirectory). Asks the user for a notebook stack choice and persists the choice to docs/superpowers/bookwright.config.yaml.

What it creates

  • book/ with chapters/, frontmatter/, appendices/, parts/, alex.sty (or empty placeholder for project's own notation), preamble.tex, references.bib, book.tex, Makefile.
  • notebooks/ (Jupyter) OR rmd/ (R Markdown) OR qmd/ (Quarto) per user choice.
  • papers/ (empty; user can git-subtree-add source papers later).
  • docs/superpowers/specs/ and docs/superpowers/plans/.
  • docs/superpowers/bookwright.config.yaml recording the notebook stack choice and other project settings (key: notebook_stack: python-uv | r-renv | quarto | none; none means prose-only and notebook-author is never dispatched).
  • book/CLAUDE.md recording the build command (matching the Makefile), the banned-phrase list, label-naming conventions, and the notebook directory. Five agents read this file; a project without it breaks the drafting chain.

Steps

  1. Ask the user (via AskUserQuestion) which notebook stack: Python+uv+Jupyter / R+renv+RMarkdown / Quarto / none.
  2. Create the directory tree.
  3. Write a minimal book.tex that includes empty parts/part1.tex and references it.
  4. Write a minimal Makefile with the standard cleanall + biber + pdflatex pipeline.
  5. Write the bookwright.config.yaml recording user choices.
  6. Write book/CLAUDE.md with: the build command from the Makefile, the banned-phrase list (seed from the soul conventions or leave a TODO section), label-naming conventions, and the notebook directory chosen in step 1.
  7. Write a README in the new project root summarizing the layout.
  8. Initialize git if not already initialized; commit the scaffold.
  9. Report success and suggest next steps: /bookwright:design master (or /bookwright:design part1).

Dependencies

  • The soul plugin should be installed in the user's Claude environment for the soul-voice hook to fire on .tex writes in the new project. init should remind the user of this if not already done.

Read the full file on GitHub · 35 lines

Changes

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.

  1. 2d ago First seen · 35 lines · 23 tokens per session scan A a573a0d124df

Subscribe to this mod's changes

init is a command published in the GitHub repository queelius/claude-anvil (2 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 596 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-31.