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 queelius/claude-anvil/plugin install kdpWrote 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/queelius/claude-anvil/kdp-publish)<a href="https://agentmods.dev/skills/queelius/claude-anvil/kdp-publish"><img src="https://agentmods.dev/badge/skills/queelius/claude-anvil/kdp-publish/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/queelius/claude-anvil/kdp-publish"><img src="https://agentmods.dev/badge/skills/queelius/claude-anvil/kdp-publish.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.04662 |
| Opus 5 | $0.00030 | $0.02331 |
| Sonnet 5 | $0.00012 | $0.00932 |
| Haiku 4.5 | $0.00006 | $0.00466 |
Grade A, and why
kdp-publish 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 10d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KDP Book Publishing Workflow
Orchestrate the full workflow for publishing a book through Amazon KDP (Kindle Direct Publishing): audit the manuscript, craft the listing, prepare files, and submit. This skill coordinates /kdp-audit and /kdp-listing into a phased pipeline, then walks through the mechanical submission steps on the KDP dashboard.
Strategy
The recommended publication sequence:
- Audit -- Verify the manuscript meets KDP formatting and content requirements
- Listing -- Craft blurb, keywords, categories, and author bio (the marketing artifacts that determine discoverability)
- Prepare -- Convert manuscript to final format, verify cover specs
- Submit -- Walk through the KDP dashboard, upload files, set pricing, publish
Each phase gates the next. Do not submit a manuscript that fails audit. Do not fill in listing fields without the artifacts from /kdp-listing. Present the phase map, confirm the plan, and proceed one phase at a time.
Workflow
Phase 1: Assess Current State
Determine where the book stands in the pipeline to skip completed phases.
Load user config (Read tool): Read .claude/kdp.local.md if it exists. Extract the kdp section and author metadata from YAML frontmatter. If the file is missing, offer to create one from the template at ${CLAUDE_PLUGIN_ROOT}/docs/user-config-template.md.
Detect manuscript files (Glob tool): Search for manuscript files in the project:
.texfiles (LaTeX -- technical books).docxfiles (Word -- fiction/nonfiction).epubfiles (eBook source).mdfiles (Markdown manuscripts).pdffiles (final output).kpffiles (Kindle Create project)
Classify the manuscript type: Technical (LaTeX, math, code), Fiction (chapters, dialog), or General nonfiction.
Check what already exists (Glob/Read tools):
- Cover files? (
cover*.jpg,cover*.pdf,paperback-cover.*,full-cover.*) - Audit already done? (Look for recent audit report in conversation history or notes)
- Listing artifacts in config? (
kdp.blurb,kdp.keywords,kdp.categoriespopulated?) - Manuscript in final format? (compiled PDF, validated EPUB)
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.
- 10d ago First seen · 298 lines · 60 tokens per session scan A a3e10d2723fc
kdp-publish is a skill published in the GitHub repository queelius/claude-anvil (2 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 4,662 once invoked, about $0.0003 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.
Other skills, from other repositories
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.
cco-tools
Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses.
alive-search
Search across all walnuts -- decisions, people, files, references, insights, log history.