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/comfuture/novelist/create-novel-projectnpx skills add comfuture/novelist --skill create-novel-projectgit clone --depth 1 https://github.com/comfuture/novelistWrote 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/comfuture/novelist/create-novel-project)<a href="https://agentmods.dev/skills/comfuture/novelist/create-novel-project"><img src="https://agentmods.dev/badge/skills/comfuture/novelist/create-novel-project.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.00056 | $0.00526 |
| Opus 5 | $0.00028 | $0.00263 |
| Sonnet 5 | $0.00011 | $0.00105 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
create-novel-project 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Novel Project
Operating Contract
Create a novel source workspace from the scaffold bundled with this plugin. The scaffold includes source directories, YAML-frontmatter templates, manuscript markup rules, visual direction, and generated-output boundaries. It does not copy another set of Agent Skills into the project; the installed Novelist plugin continues to provide them.
Before running the bundled command, resolve <skill-dir> to the absolute
directory containing this SKILL.md.
Workflow
- Resolve the destination from the user's explicit path. If no path was given, use the current directory only when it is clearly the intended workspace; otherwise ask for the destination.
- Gather a working title and BCP 47-style language tag when the user supplied
them. Both are optional: the defaults remain
Untitled Novelandko. - Inspect the destination before writing. Preserve unrelated existing files.
- Run the bundled initializer:
python3 "<skill-dir>/scripts/create_novel_project.py" \
--project-root /absolute/path/to/novel \
--title "Working Title" \
--language ko
- Do not pass
--forcemerely because the destination exists. The initializer performs a complete collision preflight and writes nothing when a scaffold file would be overwritten. Use--forceonly after the user explicitly asks to replace the plugin-managed scaffold files. - Verify
project.md,AGENTS.md, the source directories and templates, andpublished/.gitignore. Rungit status --shortwhen the destination is inside a Git repository. - Summarize the created paths and suggest the next relevant plugin skill, such
as
create-setting,create-character, orcreate-plot. Let the host apply its own invocation syntax.
Safety Rules
- Never initialize into the plugin installation itself.
- Never delete unrelated destination files.
- Never copy
.git,.codex, generated EPUB output, or project-local skill duplicates into the new workspace. - Treat the copied Markdown files as canonical source and
published/as generated output. - Do not commit unless the user asks.
What ships with it
3 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.
- 4d ago First seen · 56 lines · 56 tokens per session scan A c2b264155b99
create-novel-project is a skill published in the GitHub repository comfuture/novelist (5 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 526 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…