write-like-a-human

write-like-a-human is a skill for Claude Code, Codex from spencerpauly/skills-repo. It costs 79 tokens per session (762 once invoked), scanned A, original, MIT.

A writing skill that rewrites text to remove common signs of AI-generated prose.

In plain words
What is it for?
Use it to humanize, tighten, or de-AI blog posts, launch emails, READMEs, and other drafts.
Why use it?
It helps when text sounds padded, overly enthusiastic, repetitive, or unlike a person’s normal writing.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to humanize, tighten, or de-AI blog posts, launch emails, READMEs, and other drafts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/spencerpauly/skills-repo/write-like-a-human
Install

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.

Any agent
npx skills add spencerpauly/skills-repo --skill write-like-a-human
Clone the repo
git clone --depth 1 https://github.com/spencerpauly/skills-repo

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for write-like-a-human

README.md
[![agentmods](https://agentmods.dev/badge/skills/spencerpauly/skills-repo/write-like-a-human/github.svg)](https://agentmods.dev/skills/spencerpauly/skills-repo/write-like-a-human)
Your own site
<a href="https://agentmods.dev/skills/spencerpauly/skills-repo/write-like-a-human"><img src="https://agentmods.dev/badge/skills/spencerpauly/skills-repo/write-like-a-human/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.

agentmods 80×15 button for write-like-a-human

Your own site · 80×15
<a href="https://agentmods.dev/skills/spencerpauly/skills-repo/write-like-a-human"><img src="https://agentmods.dev/badge/skills/spencerpauly/skills-repo/write-like-a-human.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 762 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00079 $0.00762
Opus 5 $0.00039 $0.00381
Sonnet 5 $0.00016 $0.00152
Haiku 4.5 $0.00008 $0.00076

Measured 12d ago against content hash 22de44447003, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

write-like-a-human scanned grade A with 1 finding 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 12d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -fsSL https://raw.githubusercontent.com/blader/humanizer/main/SKILL.md
skills/write-like-a-human/SKILL.md · 55 lines

How it starts

The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Write Like a Human

Rewrite text so it stops sounding like a language model wrote it. Wraps the open-source humanizer skill, which catalogs ~30 specific tells (em-dash overuse, "stands as a testament", -ing analyses, rule-of-three padding, inline-bold lists, and so on).

When to use

  • The user pastes a chunk of writing and asks to "humanize", "de-AI", "tighten", or "make this sound like me".
  • The user asks for editing on something they wrote with an LLM.
  • A blog post / launch email / README draft has tells the user wants gone.

Steps

  1. Load the reference list of patterns the first time this skill activates in a session. On Spencer's machine, read the canonical local copy (newer than upstream):

    cat ~/.agents/skills/humanizer/SKILL.md
    

    Otherwise pull it from upstream:

    curl -fsSL https://raw.githubusercontent.com/blader/humanizer/main/SKILL.md
    

    There are ~30 patterns; you don't need to memorize them, just keep them visible while editing.

  2. Ask for a voice sample if you don't already have one. One paragraph the user wrote themselves is enough. Match cadence, vocabulary, and how they handle transitions. For content written as Spencer, the voice layer is the spencers-writing-style skill in the stack repo (.agents/skills/spencers-writing-style/) — use it instead of asking.

  3. Do a first pass removing the highest-signal tells in this order:

    1. Sycophantic openers ("Great question!", "Absolutely!").
    2. Em-dashes that should be commas, periods, or parens.
    3. "It's not just X, it's Y" / "Not only … but …" parallelisms.
    4. Inflated significance words: testament, pivotal, landscape, vibrant, tapestry, underscore.
    5. Rule-of-three lists that pad ideas into groups of three.
    6. Inline-bold vertical lists (- **Speed:** …).
  4. Do a second "audit" pass. Re-read your draft and ask out loud: "What still makes this sound AI-generated?" Answer briefly, then revise once more. This step is the difference between "cleaned up" and "actually sounds human".

Read the full file on GitHub · 55 lines

Changes

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.

  1. 12d ago First seen · 55 lines · 79 tokens per session scan A 22de44447003

Subscribe to this mod's changes

write-like-a-human is a skill published in the GitHub repository spencerpauly/skills-repo (25 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 762 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens