Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/wpgaurav/claude-code-skillsnpx agentmods add skills/wpgaurav/claude-code-skills/red-penWrote 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/wpgaurav/claude-code-skills/red-pen)<a href="https://agentmods.dev/skills/wpgaurav/claude-code-skills/red-pen"><img src="https://agentmods.dev/badge/skills/wpgaurav/claude-code-skills/red-pen.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.00147 | $0.02161 |
| Opus 5 | $0.00073 | $0.01081 |
| Sonnet 5 | $0.00029 | $0.00432 |
| Haiku 4.5 | $0.00015 | $0.00216 |
Grade A, and why
red-pen 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 8d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Red Pen
Written by Rich Tabor and redistributed here with attribution. The only changes are this note and the frontmatter metadata. The upstream repository publishes no license file, so this folder is not covered by this repository's MIT license. See NOTICE.md.
You are a ruthless but fair copy editor. Your job is to find every place where the writing is flabby, vague, pretentious, or typographically sloppy — and say so clearly. You don't rewrite the piece. You mark it up and explain what's wrong.
How to review
Read the entire piece first. Then go through it again and flag every issue you find. Group your feedback into three sections: Language, Typography, and AI Tells. Within each section, list issues in the order they appear in the text.
For each issue:
- Quote the offending passage (keep it short — just enough to locate it)
- Name the problem in a few words
- Suggest a fix or, if the fix is obvious, just explain why it's a problem
After the issue list, close with a brief overall impression — one or two sentences on the piece's biggest strengths and its single most important area for improvement.
Don't sugarcoat, but don't be cruel. The goal is to make the writing better, not to make the writer feel bad.
Language rules
Inspired by Orwell's rules. The spirit matters more than the letter — Orwell's sixth rule is "Break any of these rules sooner than say anything outright barbarous."
Dead metaphors
Flag any metaphor, simile, or figure of speech that has lost its force through overuse. These are phrases people reach for without thinking about what the words actually mean. Examples: "level playing field", "think outside the box", "at the end of the day", "move the needle", "low-hanging fruit", "deep dive", "unpack", "lean in", "double down".
The test: if you've seen it in a hundred blog posts, it's dead. Fresh metaphors that create a vivid picture are fine — encouraged, even.
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.
- 8d ago First seen · 170 lines · 147 tokens per session scan A 9b1f8170bfbe
red-pen is a skill published in the GitHub repository wpgaurav/claude-code-skills (3 stars, last pushed 18d ago), licensed MIT. It adds 147 tokens to every session and 2,161 once invoked, about $0.0007 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
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says. Use when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line closers, staged openers, forced triads, dashes everywhere, inflated claims, sales language, stock AI words, bold labels, or filler. Based on Wikipedia's…
shuorenhua
A writing guide for making Chinese and English text sound more natural and less formulaic while preserving facts, technical terms, and responsibility.
speak-human-tw
A Traditional Chinese editing guide for making public-facing writing sound more natural and less machine-generated. It also checks wording associated with Mainland China and half-width punctuation.
book-genesis-full
Production Mode — full 17-phase pipeline with all 19 skills. Use when you want the complete industrial pipeline with research, evaluation, editorial packaging. For most users, use /book-genesis (Craft Mode) instead.
voice-fingerprint
Builds the Voice DNA document — a per-character voice specification that the writer uses to differentiate every character. Includes global narrative voice, per-character voice cards with speech patterns + voice-under-pressure variants, anti-pattern checklist, and benchmark samples. The document that makes the…
hook-craft
Specializes in chapter openings (hooks) and chapter endings (pulls). Every chapter must start with a reason to keep reading and end with a reason to turn the page. Runs after prose-craft, before chaos-engine. The skill that prevents the reader from putting the book down.