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 skills add JHostalek/dotclaude --skill writinggit clone --depth 1 https://github.com/JHostalek/dotclaudeWrote 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/jhostalek/dotclaude/writing)<a href="https://agentmods.dev/skills/jhostalek/dotclaude/writing"><img src="https://agentmods.dev/badge/skills/jhostalek/dotclaude/writing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jhostalek/dotclaude/writing"><img src="https://agentmods.dev/badge/skills/jhostalek/dotclaude/writing.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00021 | $0.00752 |
| Opus 5.5 | $0.00008 | $0.00301 |
| Sonnet 5.5 | $0.00004 | $0.00150 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
writing 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 9d 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.
Writing
Rewrite the given text or passage as a person would write it. With no target, rewrite the last substantive agent response. Ask only when the target or intended meaning cannot be determined.
Slop is text that reads as generated: padded, generic, inflated, shaped by habits no person would choose. Each habit is a tell. references/tells.md catalogs tells for the reviewer. The writer works from the positive targets below, not the catalog.
1. Find the reader
Name the reader, what they already know, and what they must do or decide after reading. Find where the original loses them: a buried point, missing context, an unexplained term, slop. For project text, use the domain terms in the repo glossary (GLOSSARY.md, or CONTEXT.md in older repos).
Done when you can state the reader's need and the original's failure in one sentence each.
2. Study the pairs (Czech)
Read all of references/cs-pairs.md, since its moves transfer across media. Choose the pairs closest to your text's medium and register, and compare their sides on four axes: order, verbs, density, register.
Done when you can name, for each chosen pair, one move of the human side that your draft will copy.
3. Rewrite
- Lead with what the reader needs. Put the context a conclusion depends on before the conclusion.
- Write with ASD-STE100 clarity in any language: one name per thing, an explicit actor, unfamiliar terms explained.
- Carry over the author's stance. Every fact, number, and example comes from the original or the conversation. Uncertainty stays visible.
- Keep strong original sentences. Length follows content: add the context the reader lacks, and stop when the content ends.
- Match the original's language, register, and medium. Judge naturalness phrase by phrase, and draft from how a native speaker would explain the situation.
- Prose by default. Headings, bullets, and bold only where the reader navigates.
What ships with it
4 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.
- 9d ago Changed · +11 lines adf9bb2df876
- 1mo ago First seen · 45 lines · 21 tokens per session scan A b499d7601356
writing is a skill published in the GitHub repository JHostalek/dotclaude (11 stars, last pushed 3d ago), licensed CC0-1.0. It adds 21 tokens to every session and 752 once invoked, about $0.0001 per session on Opus 5.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-09-11.
Other skills, from other repositories
pulser
Diagnose and test Claude Code skills against Anthropic's 7 principles. Scans SKILL.md files, checks 8 rules (gotchas, description, allowed-tools, file-size, structure, frontmatter, conflicts, usage-hooks), classifies skill types, generates prescriptions, and runs eval tests. Use when checking skill quality, auditing…
poteto-mode
Bundled skills live at ../ /SKILL.md from this file, so put this file's absolute path in every poteto-agent prompt.
teach
Explain a body of work plainly so a person actually understands it. Runs the how and why skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
create-formal-verification-skill
Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /create-formal-verification-skill, "model-check this race", "prove this invariant", or when concurrency, retries, state machines, parsers…
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
principle-type-system-discipline
Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, exhaust variants, derive from authoritative schemas.