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-settingnpx skills add comfuture/novelist --skill create-settinggit clone --depth 1 https://github.com/comfuture/novelistWhat 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.00062 | $0.00756 |
| Opus 5 | $0.00031 | $0.00378 |
| Sonnet 5 | $0.00012 | $0.00151 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
create-setting 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Setting
Overview
Use this skill to turn a rough novel-setting prompt into a complete world/*.md source file.
Always follow AGENTS.md and world/_template.md. Generate useful defaults from the user's prompt, but keep the process interactive: reflect the inferred setting, ask for missing information and direction, revise from feedback, then write only after the user confirms.
Before running a bundled command, resolve <skill-dir> to the absolute directory
containing this SKILL.md. This keeps the same skill usable from either the
repository-local skill tree or the Novelist plugin.
Workflow
1. Read Context
Read:
AGENTS.mdproject.mdworld/_template.md- Existing files in
world/ - Relevant
plot/,outlines/,materials/,macguffins/, andcharacters/files if the prompt references them
2. Generate A Setting Draft
From the user's prompt, infer a compact first-pass setting in Korean. Include:
- era and time scale
- primary region and key locations
- social order, institutions, class pressure, and power structure
- material culture and technology level
- atmosphere, sensory palette, and recurring visual motifs
- rules or constraints that affect plot
- continuity facts that should not drift
- open questions and missing decisions
Mark inferred items clearly. Do not present guesses as fixed canon.
3. Ask For Direction
Ask the user what to add, remove, sharpen, or decide. The question must focus on missing information and authorial direction, not on generic brainstorming.
Good prompts:
- "시대는 조선 후기 그대로 둘까요, 아니면 가상의 왕조로 비틀까요?"
- "이 세계의 핵심 압박을 정치, 가족, 종교, 경제 중 어디에 두면 좋을까요?"
- "현실 고증을 강하게 가져갈지, 분위기 우선으로 변형할지 선택해주세요."
Continue the feedback loop until the user says it is enough or gives enough detail to save.
4. Build The Setting File
Use a filesystem-safe ASCII slug. Save to world/<slug>.md; id must be world-<slug>.
Required frontmatter:
id: world-ascii-slug
type: world
title: ""
category: setting
status: seed
time_period: ""
locations: []
rules: []
related_characters: []
related_materials: []
used_in_chapters: []
created: YYYY-MM-DD
updated: YYYY-MM-DD
tags: []
What ships with it
2 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.
- 2d ago First seen · 98 lines · 62 tokens per session scan A e667bb96b6aa
create-setting is a skill published in the GitHub repository comfuture/novelist (5 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 756 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.