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 lguz/humanize-writing-skill --skill humanize-writinggit clone --depth 1 https://github.com/lguz/humanize-writing-skillWrote 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/lguz/humanize-writing-skill/humanize-writing)<a href="https://agentmods.dev/skills/lguz/humanize-writing-skill/humanize-writing"><img src="https://agentmods.dev/badge/skills/lguz/humanize-writing-skill/humanize-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/lguz/humanize-writing-skill/humanize-writing"><img src="https://agentmods.dev/badge/skills/lguz/humanize-writing-skill/humanize-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.00073 | $0.02606 |
| Opus 5 | $0.00036 | $0.01303 |
| Sonnet 5 | $0.00015 | $0.00521 |
| Haiku 4.5 | $0.00007 | $0.00261 |
Grade A, and why
humanize-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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Humanize Writing
You're a writing editor. Your one job is making text sound like a real person wrote it, not a language model. That means finding the patterns that scream "AI wrote this" and replacing them with something a human would actually write.
Good writing sounds like a smart person thinking out loud. Sometimes that's a short sentence. Sometimes it's a longer one that lets an idea breathe. The point is that every sentence earns its place and nothing is there just to sound impressive. Write to be understood, not to perform.
When to Use
- User shares text and wants it to sound more human or natural
- User says "this sounds like AI," "make it less ChatGPT," or "humanize this"
- Editing LinkedIn posts, blog drafts, emails, or marketing copy for voice
- User shares a draft and wants it to feel more authentic
When NOT to Use
- Technical writing: docs, READMEs, API references, code comments
- User explicitly wants formal or academic tone
- The text is already in the user's natural voice and they're happy with it
- Commit messages, changelogs, or structured data
Before You Start
Read references/ai-patterns-dictionary.md in this skill's directory. That's your
playbook — the full list of banned words, banned structures, and tone tells. Know it
before you touch anything.
Pick a Voice
Read references/voices.md for the full voice definitions. Before rewriting, you
need to know which voice to write in. Follow this order:
1. User already specified a voice? Use it. They might say "make it punchy" (use sharp-opinionated), "keep it professional" (use warm-professional), or name a voice directly.
2. User provided writing samples? Use the mirror voice. Study their samples and build a custom voice profile using the dimensions in voices.md. Don't describe the profile to them — just apply it. If they also show you writing they don't like, that's equally valuable. Study what makes it feel wrong to them.
3. Neither specified nor samples provided? Ask. Keep it quick and natural:
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.
- 9d ago First seen · 235 lines · 73 tokens per session scan A 527b186cb10c
humanize-writing is a skill published in the GitHub repository lguz/humanize-writing-skill (46 stars, last pushed 6mo ago), licensed MIT. It adds 73 tokens to every session and 2,606 once invoked, about $0.0004 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-30.
Other skills, from other repositories
blog
Full-lifecycle blog engine with 31 sub-skills, 12 content templates, 5-category 100-point scoring, and 5 specialized agents. Routes user requests to the right sub-skill: writing, rewriting, analysis, outlines, audits, schema, charts, images, repurposing, AI citation SEO, FLOW framework prompts, topic-cluster…
blog-cluster
Semantic topic cluster planning and automated execution engine for claude-blog. Performs SERP-based keyword research, groups keywords by search intent and SERP overlap, builds a hub-and-spoke cluster architecture, generates an interactive SVG cluster map, and executes the full cluster by orchestrating blog-write calls…
blog-rewrite
Rewrite and optimize existing blog posts for Google SEO (May 2026 Core Update, March 2026 core/spam context, June 2026 spam context, E-E-A-T) and AI citation visibility as one SEO discipline. Full rewrite for both Google rankings AND AI citations. For AI-citation-only audit (no Google work), use blog-geo instead.…
blog-strategy
Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI Overviews, distribution channel planning (YouTube, Reddit, review platforms for AI-citation SEO), content scoring…
blog-write
Write new blog articles from scratch optimized for Google rankings and AI citations. Generates full articles with template selection, answer-first formatting, Key Takeaways summary box, information gain markers, citation capsules, sourced statistics, Pixabay/Unsplash images, built-in SVG chart generation, optional FAQ…
blog-analyze
Audit and score blog posts on a 5-category 100-point scoring system covering content quality, SEO optimization, E-E-A-T signals, technical elements, and AI citation readiness. Includes AI content detection (burstiness, phrase flagging, vocabulary diversity). Supports export formats (markdown, JSON, table) and batch…