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/writing-principlesnpx skills add Natsummerance/readMD --skill writing-principlesgit 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/writing-principles)<a href="https://agentmods.dev/skills/natsummerance/readmd/writing-principles"><img src="https://agentmods.dev/badge/skills/natsummerance/readmd/writing-principles.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.00041 | $0.01080 |
| Opus 5 | $0.00020 | $0.00540 |
| Sonnet 5 | $0.00008 | $0.00216 |
| Haiku 4.5 | $0.00004 | $0.00108 |
Grade A, and why
writing-principles 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.
This is a copy
97% identical to writing-principles — 3 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Principles
Load /llm-writing if it isn't already loaded. This skill adds the
fiction-specific layer.
Trust the Reader
The reader is an active collaborator. They reconstruct emotions from behavior, infer motives from action, hold tension across scenes, fill gaps the text leaves open, and make assumptions about what's coming next. That work is where the reward lives: reconstruction, inference, anticipation.
Your training pulls in the opposite direction. The helpfulness instinct wants to explain, resolve, clarify, and complete. In fiction, every one of those impulses can damage the reading experience by doing work the reader wanted to do themselves. The specific failure modes below are all forms of this: not trusting the reader to interpret an emotion, hold an ambiguity, follow subtext, or tolerate unresolved tension.
Trust doesn't mean obscurity. Readers also need coherent narrative, stable geography, and enough access to model characters. The discipline is knowing when to leave space and when to orient.
Economy
Every element does more than one thing. A line of dialogue advances plot AND reveals character. A sensory detail grounds the scene AND shows who the POV character is. A transition compresses time AND carries an emotional beat. Single-purpose prose makes fiction go flat: description that only describes, dialogue that only informs, interiority that only labels.
Economy isn't minimalism. Dense, lyrical prose can be economical when every phrase carries weight. Sparse prose can be wasteful when it takes ten short sentences to do what one image could do. The measure is whether removing the element would cost the reader something.
The LLM pull is toward completeness: covering every beat, naming every emotion, resolving every ambiguity. Economy is the counter-discipline: what can you leave out and still have the scene work? What's the reader already doing for you?
Reader Reward Channels
Readers enjoy fiction through overlapping reward channels. Good prose protects the relevant channels at once; damaging one damages the reading experience.
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.
- 4d ago First seen · 107 lines · 41 tokens per session scan A 0e4527012ada
writing-principles is a skill published in the GitHub repository Natsummerance/readMD (21 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 1,080 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to writing-principles, differing in 3 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.
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…
computer-use
Windows 桌面自动化执行规则。使用 screeninteractor 观察与操作原生桌面应用。.
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.