A blog-editing workflow for rewriting Markdown or MDX posts in a specific house style and removing common signs of AI-written prose.

Use it after drafting or heavily editing a blog post. It checks the project's voice and citation rules, revises the prose, and performs a final review for obvious AI patterns.

It helps keep blog writing consistent and makes drafts sound less formulaic. It also limits the workflow to blog content, where a different writing style may be required.

How gigsmart/haiku-method configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to gigsmart/haiku-method. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/gigsmart/haiku-method/main/.claude/skills/humanize/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/gigsmart/haiku-method

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gigsmart/haiku-method/humanize/github.svg)](https://agentmods.dev/skills/gigsmart/haiku-method/humanize)

Your own site

<a href="https://agentmods.dev/skills/gigsmart/haiku-method/humanize"><img src="https://agentmods.dev/badge/skills/gigsmart/haiku-method/humanize/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gigsmart/haiku-method/humanize"><img src="https://agentmods.dev/badge/skills/gigsmart/haiku-method/humanize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,862 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00068	$0.01862
Opus 5.5	$0.00027	$0.00745
Sonnet 5.5	$0.00014	$0.00372
Haiku 4.5	$0.00007	$0.00186

Measured 2mo ago against content hash 3b65511dcbad, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

humanize 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 2mo 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.

.claude/skills/humanize/SKILL.md · 106 lines

How it starts

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

Humanize: H·AI·K·U voice + AI-tell removal

This skill runs a layered editing pass on blog prose. It is scoped to website/content/blog/**/*.{md,mdx}. Do not invoke it on UI copy, READMEs, doc pages, or paper revisions — those have a different register.

Order of operations

The passes run in this order. Earlier passes win when they conflict with later ones.

Load the voice rules. Read .claude/rules/content-voice.md and .claude/rules/citations.md before touching prose. These define the register and override anything below.
Voice-first edit. Bring the draft into compliance with content-voice.md: contractions, no hedging, hook in the first two sentences, prose over bullet lists, every claim grounded per the No-Empty-Authority rule, citations linked or paths named per citations.md.
AI-tell sweep. Apply the pattern list in this file — but only where it doesn't fight the voice rules. The conflicts are listed explicitly below; respect them.
Self-audit. Run the final "what makes this obviously AI?" pass. Answer briefly. Then revise.

Where voice beats the generic humanizer

The standard AI-tell rules are useful but blunt. The voice is specific, and these overrides apply:

Em-dashes are allowed — particularly in long-form prose where rhythm matters. Don't blanket-replace them with commas. Ban only the AI-cadence em-dash that introduces a marketing flourish ("a seamless experience — designed for you").
The rule of three is allowed when earned. The voice actively uses three-beat constructions. Strip them only when they're hollow ("efficient, scalable, and powerful"), not when each beat carries weight.
First-person plural OR singular, not generic. Either "we" (project perspective) or "I" (Jason's specific anecdote). Pick one per post and stay in it. The generic humanizer's "use I when it fits" loses to the explicit register pick.
Cap "X isn't Y. It's Z." at two uses per article, per content-voice.md. The humanizer's "negative parallelism" rule aligns here, but the cap is stricter.
Coined phrases stay. When the draft names a pattern ("the continuity contract", "the workshop has two editors"), don't flatten it back to plain language. Coining is a feature, not a tell.
Contractions are required, not optional.
No hypothetical numbers, even framed as such. Replace with a real, named, verifiable thing — a commit SHA, a file path, a test case, a CI run — or cut the claim.
No emojis. Straight quotes. Sentence-case headings.

Read the full file on GitHub · 106 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.

2mo ago First seen · 106 lines · 68 tokens per session scan A 3b65511dcbad

Subscribe to this mod's changes

humanize is a skill published in the GitHub repository gigsmart/haiku-method (29 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 68 tokens to every session and 1,862 once invoked, about $0.0003 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-08-30.

Writing and docs ai ai-agents ai-dlc claude development-lifecycle methodology

humanize next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
humanizegigsmart/haiku-method	Skill	29	5mo ago	Apache-2.0	A	68	Claude Code
sparc-methodologyruvnet/RuView	Skill	103k	today	MIT	A	29	Claude Code
contradiction-analysisHughYau/qiushi-skill	Skill	3.9k	1mo ago	MIT	A	184	Claude Code
mass-lineHughYau/qiushi-skill	Skill	3.9k	1mo ago	MIT	A	195	Claude Code
practice-cognitionHughYau/qiushi-skill	Skill	3.9k	1mo ago	MIT	A	183	Claude Code
protracted-strategyHughYau/qiushi-skill	Skill	3.9k	1mo ago	MIT	A	211	Claude Code
methodology-curatorathola/claude-night-market	Skill	348	today	MIT	A	21	Claude Code

haiku-method: Skill for Claude Code