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 agentmods add skills/voidtechnology/voidtech-claude-plugins/text-naturalizernpx skills add VoidTechnology/voidtech-claude-plugins --skill text-naturalizergit clone --depth 1 https://github.com/VoidTechnology/voidtech-claude-pluginsWhat 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 | $0.00066 | $0.00941 |
| Opus 5 | $0.00033 | $0.00470 |
| Sonnet 5 | $0.00013 | $0.00188 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
text-naturalizer 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 yesterday.
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.
What it actually says
VoidTech 原创技能
文本自然化
把中文、英文或中英混排文本改成更像真人写的版本。目标不是“更华丽”，而是更准确、更有节奏、更符合语境。
工作流
- 判断文本语言与体裁：中文、英文、中英混排；博客、邮件、产品文案、技术文档、论文、PR 描述、社媒、个人表达等。
- 按语言读取参考：
- 中文或中英混排：读取
references/chinese-patterns.md。 - 英文或中英混排：读取
references/english-patterns.md。
- 中文或中英混排：读取
- 校准声音：如果用户给了本人样例，优先模仿样例的句长、词汇密度、段落习惯、标点偏好和态度强度。
- 审计 AI 痕迹：找出套话、过度铺垫、宣传腔、三段式、虚假深刻、模糊归因、聊天机器人残留、过度整齐的节奏。
- 重写而不是删空：保留原文信息覆盖面。不要为了显得自然而丢掉关键事实、限定条件、术语或作者立场。
- 做一次反向检查：问自己“这版还有哪里像 AI 生成？”然后修掉最明显的残留。
硬约束
- 不编造事实、引用、数据、人物、机构或来源。原文不确定时，改成明确的不确定表达，或在合适场景中删除该句。
- 不把所有文本都改成口语。技术、法律、学术、百科和接口文档应该自然但克制。
- 不强行加入观点、幽默、第一人称或情绪。只有个人文章、评论、演讲稿、社媒和品牌文案适合加明显声音。
- 不过度同义改写。术语、产品名、API 名、变量名、标题层级和专有名词保持稳定。
- 不保留聊天机器人开场和收尾，例如“当然可以”“希望这有帮助”“如果你需要我继续”。
- 默认去掉装饰性 emoji、机械粗体、标题式列表、泛泛总结和口号式结尾，除非用户明确要求保留格式。
语言策略
中文优先处理这些问题：翻译腔、抽象名词堆叠、过度连接词、“不仅……更……”“从……到……”、宏大意义拔高、“赋能/打造/助力/生态/闭环”等营销套话，以及段尾金句。
英文优先处理这些问题：significance inflation, promotional adjectives, superficial -ing clauses, vague attribution, rule-of-three lists, em dash overuse, title-case headings, chatbot artifacts, hedging pileups, and slogan-like closers.
中英混排时：
- 中文段落按中文节奏改，英文句子按英文习惯改。
- 保留必要英文术语，不把稳定术语硬翻译成中文。
- 不用中式连接词串起英文短语，也不用英文营销腔污染中文句子。
- 统一标点风格，但不要为了统一牺牲项目已有写法。
输出
默认只给最终改写文本。用户需要审阅过程时，再给：
- 主要 AI 痕迹
- 修改策略
- 最终版本
如果是修改文件，直接编辑文件并在回复中说明文件路径与验证方式。若用户要求“保留结构”，保持段落数量、标题层级和列表结构；若用户要求“只润色”，不要大幅重组。
来源
本 skill 重新组织并改写了以下 MIT 项目的思路：blader/humanizer 与 op7418/Humanizer-zh。详细许可证见 LICENSE。
What ships with it
3 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.
- yesterday First seen · 58 lines · 66 tokens per session scan A f3e5709d8b37
text-naturalizer is a skill published in the GitHub repository VoidTechnology/voidtech-claude-plugins (2 stars, last pushed 28d ago), licensed Apache-2.0. It adds 66 tokens to every session and 941 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…