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 skills add DukeTwoCan/autonovel-agent-skills --skill autonovel-exportgit clone --depth 1 https://github.com/DukeTwoCan/autonovel-agent-skillsWrote 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/duketwocan/autonovel-agent-skills/autonovel-export)<a href="https://agentmods.dev/skills/duketwocan/autonovel-agent-skills/autonovel-export"><img src="https://agentmods.dev/badge/skills/duketwocan/autonovel-agent-skills/autonovel-export/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/duketwocan/autonovel-agent-skills/autonovel-export"><img src="https://agentmods.dev/badge/skills/duketwocan/autonovel-agent-skills/autonovel-export.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.00090 | $0.02139 |
| Opus 5 | $0.00045 | $0.01069 |
| Sonnet 5 | $0.00018 | $0.00428 |
| Haiku 4.5 | $0.00009 | $0.00214 |
Grade A, and why
autonovel-export 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 12d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonovel — Phase 4 (Export)
Typeset the completed novel and produce final deliverables.
When to use this skill
- State.json shows
"phase": "export"(set by consistency-pass when cycles exhausted) - User says "export the novel" / "build the PDF" / "make the ePub"
Prerequisites
!`cd "$AUTONOVEL_WORKSPACE/$NOVEL_SLUG" && ls chapters/*.md | wc -l && cat state.json | python -c "import json,sys; s=json.load(sys.stdin); print(s.get('phase'), s.get('chapters_drafted'))"`
Need: all chapters drafted, state.json phase is "export" (or user explicitly overriding).
For PDF: use a local xelatex/pdflatex installation or the repository's
optional container toolchain. Check for a local engine:
!`which pdflatex || which xelatex || echo "no LaTeX engine found"`
If neither is found, look for compose.tools.yaml at the repository root and
use the container command in Step 3. If neither native LaTeX nor Docker is
available, skip PDF with a warning; ePub and transcript chunks still work.
Workflow
Step 0 — Unpaid foreshadow check
If story_state/facts.json does not exist, skip this step silently — the
novel predates the story-state ledger (Module A) and has no foreshadow
tracking. Otherwise run:
!`python3 ${HERMES_SKILL_DIR}/lib/story_state.py unpaid "$AUTONOVEL_WORKSPACE/$NOVEL_SLUG/story_state/facts.json"`
If any items print, list them to the user with their setup chapters before proceeding. Export continues regardless (a dangling thread may be intentional / sequel-bait) — this is a warning, not a gate.
Step 1 — Confirm title and author
Read state.json for novel_slug. Ask the user for the title (display title, may differ from slug) and author byline.
Step 2 — Content-notes front matter (if applicable)
Read profile from state.json and read the normalized selected packs from
genre_context/resolved.json's selected_pack_ids. Let Intimacy be selected
only when "intimacy" is in that list; do not re-resolve pack selection from
display tags. A non-empty profile.content_tags still implies Intimacy because
the resolver records "intimacy" in selected_pack_ids for that profile. If
profile.rating is M or E, or Intimacy is selected, build a content-notes
line:
What ships with it
6 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.
- 12d ago First seen · 182 lines · 90 tokens per session scan A a325822c5d0c
autonovel-export is a skill published in the GitHub repository DukeTwoCan/autonovel-agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 2,139 once invoked, about $0.0005 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
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
pdf-extract-create-workflow
Complete PDF lifecycle: download, extract, and generate structured documents with reportlab.
document-direct-python
Use direct Python execution for reliable document creation including spreadsheets, PDFs, and structured reports.
pdf-text-extraction-fallback-85d5ca
Fallback workflow for extracting text from PDFs when readfile returns binary data.
pdf-verification-cli
Verify PDF page count and content using command-line tools when Python libraries unavailable.