Borrowing it
Nothing to install: this file belongs to AHepi/DeepReason. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AHepi/DeepReason/main/.claude/skills/pinker-write-for-readers/SKILL.mdgit clone --depth 1 https://github.com/AHepi/DeepReasonWrote 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/ahepi/deepreason/pinker-write-for-readers)<a href="https://agentmods.dev/skills/ahepi/deepreason/pinker-write-for-readers"><img src="https://agentmods.dev/badge/skills/ahepi/deepreason/pinker-write-for-readers.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.1 | $0.00099 | $0.01605 |
| Opus 5 | $0.00049 | $0.00803 |
| Sonnet 5 | $0.00020 | $0.00321 |
| Haiku 4.5 | $0.00010 | $0.00161 |
Grade A, and why
pinker-write-for-readers 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pinker: Write for Readers
Help one mind reconstruct a truthful, coherent model from a linear string of words. Preserve the author's meaning, warranted uncertainty, voice, genre, and obligations while reducing the work that comes from missing context or avoidable structure.
Choose the mode
- Draft: Build prose from notes, evidence, or a communication brief.
- Revise: Return improved prose and explain material changes at the level the user wants.
- Audit: Diagnose the highest-impact reader problems without rewriting unless requested.
- Teach: Use contrast, guided rewriting, and reader-effect explanations to develop transferable judgment.
- Explain the method: Distinguish Pinker's advice from borrowed traditions and this skill's implementation choices.
Read references/writing-evidence.md when attribution or research support matters. Read references/revision-diagnostics.md for a diagnostic sequence and edit-report format.
Establish the communication brief
Identify subject, purpose, audience, medium, genre, register, length, stakes, house style, source constraints, and content that must not change. Infer low-risk details when possible. Ask only when a missing choice would materially change the result.
Build an internal reader ledger: what the reader likely knows, what must be introduced, which terms are legitimate, which assumptions require explanation, and what the reader should understand or do after reading. Show it only when the user requests process detail or when unresolved assumptions materially affect the answer.
Draft or revise in dependency order
1. Secure truth and meaning
Check claims, evidence, quotations, logical validity, attributions, scope, and uncertainty. Never improve apparent confidence by removing a qualification that changes the proposition. Verify current or externally checkable claims when the task requires it.
2. State the topic and point
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 · 99 lines · 99 tokens per session scan A f53a03b4b71f
pinker-write-for-readers is a skill published in the GitHub repository AHepi/DeepReason (142 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 1,605 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…