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-visual-assetnpx skills add comfuture/novelist --skill create-visual-assetgit 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-visual-asset)<a href="https://agentmods.dev/skills/comfuture/novelist/create-visual-asset"><img src="https://agentmods.dev/badge/skills/comfuture/novelist/create-visual-asset.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.00062 | $0.01223 |
| Opus 5 | $0.00031 | $0.00611 |
| Sonnet 5 | $0.00012 | $0.00245 |
| Haiku 4.5 | $0.00006 | $0.00122 |
Grade A, and why
create-visual-asset 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 3d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Visual Asset
Overview
Use this skill to create project-bound cover and illustration assets for the novel.
Always preserve visual consistency by reading style/visual-style-guide.md
first. Detect the image-generation capabilities available in the current host,
then use the matching guide:
- Codex:
references/codex-image-generation.md - Claude Code:
references/claude-image-generation.md - Antigravity CLI:
references/antigravity-image-generation.md - External API or CLI provider:
references/external-image-provider.md
Save final project-bound assets under assets/cover/ or
assets/illustrations/; never leave a referenced asset only in a provider's
default output location.
Required Context
Read before generating:
AGENTS.mdproject.mdstyle/visual-style-guide.md- relevant
chapters/*.md,outlines/,plot/,world/,characters/,materials/, andmacguffins/files for the requested asset - existing files in
assets/cover/andassets/illustrations/
If style/visual-style-guide.md is incomplete, ask the user for missing visual direction before generating a final asset.
Workflow
1. Identify Asset Type
Classify the request as one of:
cover: front cover image for EPUB packagingchapter-illustration: full-width or full-page illustration tied to a chapterspot-illustration: smaller image embedded within a chaptermotif: reusable visual symbol, object, or atmospheric platereference: visual exploration not yet used in the manuscript
Confirm the intended destination and filename slug before saving.
2. Gather Direction
Summarize the likely image in Korean:
- subject
- narrative moment or symbolic function
- setting and time period
- characters shown or deliberately omitted
- composition and crop
- mood, lighting, palette, and texture
- continuity constraints from source files
- whether text should be included
Ask for missing direction when it affects the image. For covers, ask about tone, central image, and whether the title/author text should be left out for later typography. Prefer no generated text unless the user explicitly asks for it.
What ships with it
7 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.
- agents/openai.yaml 204 B
- references/antigravity-image-generation.md 753 B
- references/claude-image-generation.md 699 B
- references/codex-image-generation.md 606 B
- references/external-image-provider.md 2.7 KB
- scripts/invoke_image_provider.py 5.0 KB runs code
- tests/test_invoke_image_provider.py 2.9 KB runs code
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.
- 3d ago First seen · 145 lines · 62 tokens per session scan A ac0631795159
create-visual-asset 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 1,223 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…