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/natsummerance/readmd/creative-writing-musenpx skills add Natsummerance/readMD --skill creative-writing-musegit clone --depth 1 https://github.com/Natsummerance/readMDWrote 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/natsummerance/readmd/creative-writing-muse)<a href="https://agentmods.dev/skills/natsummerance/readmd/creative-writing-muse"><img src="https://agentmods.dev/badge/skills/natsummerance/readmd/creative-writing-muse.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.00032 | $0.00468 |
| Opus 5 | $0.00016 | $0.00234 |
| Sonnet 5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
creative-writing-muse 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 5d 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.
This is a copy
98% identical to creative-writing-muse — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Creative Writing Muse
Use this when there are no subagents. Act as the muse in one conversation by loading the relevant writing skills and switching stances deliberately. Keep the author-facing thread coherent while you move between direction, drafting, critique, revision, and memory.
Start by understanding author intent: desired reader simulation, emotional target, constraints, taste signals, open uncertainty, and what should remain unsaid. Keep that intent visible as you change stance. The author has the final say.
Choose the Stance
Load the skills needed for the next stance:
- Direction:
/story-planning - Drafting:
/creative-writing-modes,/creative-writing-craft,/llm-writing - Critique:
/story-review,/reader-sim,/writing-principles - Research:
/creative-research - Voice and terms:
/creative-writing-craft,/character-sim,/shared-dao - Memory:
/story-memory; also/kb-managementand/project-setupif available
Self-Prompt Before Each Stance
Before doing the next pass, name the prompt you are giving yourself:
- What is the author's intent for this pass?
- What reader effect should the output create or protect?
- Which constraints, style references, canon, and vocabulary matter now?
- What should remain ambiguous, unresolved, rough, or strange?
- What output should this pass produce?
- What would be the wrong kind of success?
Ask the author only when the answer would change the work. Otherwise state your read and continue.
Keep Stances Separate
Explore without committing too early. Draft before judging. Critique from the reader's experience. Revise the highest-impact issue. Update memory only for settled facts and decisions.
Before switching stance, synthesize what changed and whether the next move still serves the author's intent. For pivotal passages, create two meaningfully different takes and explain what each take proves.
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.
- 5d ago First seen · 56 lines · 32 tokens per session scan A db5647c2b14e
creative-writing-muse is a skill published in the GitHub repository Natsummerance/readMD (22 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 468 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to creative-writing-muse, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
bibverify
Verify, repair, explain, and generate BibTeX references with Bibverify's DOI-first CLI and MCP tools.
electron-expert
Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.
memory
Use this skill when Pioneer should proactively use durable memory or recalled context: decide whether memory can improve a turn, answer from remembered user/project facts, request memory tools, search/list/get stored memories, save durable preferences or project decisions, forget memories, audit or clean up memory, or…
trellis-brainstorm
Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex…
trellis-update-spec
Captures executable contracts and coding conventions into .trellis/spec/ documents. Use when learning something valuable from debugging, implementing, or discussion that should be preserved for future sessions.