humanizer

humanizer is a skill for Claude Code, Codex from jiushiwon/wg-skills. It costs 56 tokens per session (2,713 once invoked), scanned A, original, Apache-2.0.

A writing aid that rewrites text to sound more like a person wrote it while keeping its meaning and facts. It removes common artificial-sounding patterns without adding unsupported details.

In plain words
What is it for?
Use it to revise drafts, documentation, and other text when you want a more natural style or want to match a supplied writing sample.
Why use it?
It helps when generated text feels repetitive, exaggerated, or unlike the intended writer. It preserves the original information instead of inventing examples or claims.

Skill for Claude CodeCodex

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

Good fit Use it to revise drafts, documentation, and other text when you want a more natural style or want to match a supplied writing sample.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jiushiwon/wg-skills/humanizer
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 jiushiwon/wg-skills --skill humanizer
Clone the repo
git clone --depth 1 https://github.com/jiushiwon/wg-skills

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 humanizer

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jiushiwon/wg-skills/humanizer"><img src="https://agentmods.dev/badge/skills/jiushiwon/wg-skills/humanizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,713 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00056 $0.02713
Opus 5 $0.00028 $0.01357
Sonnet 5 $0.00011 $0.00543
Haiku 4.5 $0.00006 $0.00271

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

Security

Grade A, and why

humanizer 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 6d 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.

others/humanizer/SKILL.md · 211 lines

How it starts

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

Humanizer: 去除AI写作模式

让AI生成的文字读起来像人写的,不改变原意。基于维基百科"AI写作迹象"项目(WikiProject AI Cleanup)维护的35个模式。

核心原则

  1. 保留所有事实。可以缩短冗余部分、扩展有用内容、合并或拆分段落,但信息不能丢。
  2. 不编造细节。不添加原文没有的事实、人名、数字、日期、引文或引用。如果句子缺少必要细节,要么问用户,要么用更简单的句子。
  3. 匹配作者风格。根据文本类型使用合适的语气(正式/随意/技术性)。只有在文本和作者需要时才加入个性。
  4. 允许不完美。人写的文章会有犹豫、自我修正、不均匀的节奏——这些是人的痕迹,不要删掉。

使用方式

直接调用:

/humanizer
[粘贴文本]

或用自然语言:

帮我去除这段文字的AI味道:[粘贴文本]

重写文件:

去掉 docs/launch-post.md 的AI味道

匹配你的风格

如果想让重写更像你自己的风格,附上样本:

/humanizer

以下是我写的样本:
[粘贴2-3段你自己的文字]

帮我改掉这段的AI味道:
[粘贴AI生成的文本]

35个AI写作模式

内容模式

# 模式 示例(改前) 示例(改后)
1 夸大重要性 "标志着区域统计学演进的关键时刻" "1989年成立,是西班牙行政权力下放的一部分"
2 名人背书 "被纽约时报、BBC、金融时报引用" "被纽约时报和BBC引用"
3 浅层-ing分析 "象征着...反映...展示..." 只保留原文支持的内容
4 销售话术 "坐落在令人叹为观止的地区" "是埃塞俄比亚贡德尔地区的一个城镇"
5 模糊来源 "专家认为它起着关键作用" 要么给出具体来源,要么删除该说法
6 公式化挑战与展望 "尽管面临挑战...持续蓬勃发展" 保留事实,删除套话

语言和语法模式

# 模式 示例(改前) 示例(改后)
7 AI高频词 "实际上...此外...关键...深入...展示" "也...需要...仍然常见"
8 回避is/are "作为...拥有...提供" "是...有"
9 Not X but Y "不仅仅是X,更是Y" 直接陈述观点
10 强制三连 "创新、灵感和洞察" 按实际需要的数量
11 同义词替换/重复开头 "主角...主人公...英雄" 用同一个名称,或合并重复句子
12 虚假范围 "从大爆炸到暗物质" 直接列出主题
13 被动语态 "无需配置文件" "你不需要配置文件"

风格模式

# 模式 示例(改前) 示例(改后)
14 破折号滥用 "机构——不是人民——" "机构,不是人民,"
15 加粗过多 "OKRsKPIsBMC" "OKRs、KPIs、BMC"
16 列表+粗体小标题 "性能: 性能提升..." "更新改善了界面,加快了加载速度..."
17 标题大写 "战略谈判与合作伙伴关系" "战略谈判与合作关系"
18 Emoji "🚀 启动阶段:💡 关键洞察:" 删除emoji
19 花引号 他说"项目在正轨上" 他说"项目在正轨上"
26 过多连字符词 "跨职能、数据驱动、面向客户" 只保留语法需要的连字符
27 假装揭示深层真相 "本质上,真正重要的是..." 直接陈述观点
28 预告下一点 "让我们深入了解" 直接开始内容
29 标题重复 "## 性能" + "速度很重要。" 让标题自己说话
30 描述旧版本 "此函数用于替代之前的..." 描述它现在做什么
31 强制金句 "它没有偏好。没有先验。没有怀旧。" 用自然长度的句子和具体说法
32 公式化格言 "对称是信任的语言" 陈述具体观点
33 假装坦诚 "老实说?这取决于..." 直接回答
34 回答没人问的反对 "这不是主要关于..." 删除无依据的辩护
35 否定虚假选项 "一个诱人的选择是...但是" 删除假选项,保留真正选择

Read the full file on GitHub · 211 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. 6d ago First seen · 211 lines · 56 tokens per session scan A bdfa32b87270

Subscribe to this mod's changes

humanizer is a skill published in the GitHub repository jiushiwon/wg-skills (100 stars, last pushed 2d ago), licensed Apache-2.0. It adds 56 tokens to every session and 2,713 once invoked, about $0.0003 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-06.

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