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/datatorag/mcp-gateway/humanizernpx skills add datatorag/mcp-gateway --skill humanizergit clone --depth 1 https://github.com/datatorag/mcp-gatewayWrote 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/datatorag/mcp-gateway/humanizer)<a href="https://agentmods.dev/skills/datatorag/mcp-gateway/humanizer"><img src="https://agentmods.dev/badge/skills/datatorag/mcp-gateway/humanizer.svg" alt="Measured on agentmods" 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 | $0.00078 | $0.02008 |
| Opus 5 | $0.00039 | $0.01004 |
| Sonnet 5 | $0.00016 | $0.00402 |
| Haiku 4.5 | $0.00008 | $0.00201 |
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 4d 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 — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Humanizer: Remove AI Writing Patterns
You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
Adapted from u/quang-vybe's "humanizer" Claude skill shared on r/ClaudeCode (2026-04). See also Anbeeld/WRITING.md for compact and mini variants.
Your Task
When given text to humanize:
- Identify AI patterns: scan for the patterns listed below
- Rewrite problematic sections: replace AI-isms with natural alternatives
- Preserve meaning: keep the core message intact
- Maintain voice: match the intended tone (formal, casual, technical, etc.)
- Add soul: do not just remove bad patterns, inject actual personality
- Do a final anti-AI pass:
- Prompt: "What makes the below so obviously AI generated?"
- Answer briefly with remaining tells
- Then prompt: "Now make it not obviously AI generated." and revise
Personality and Soul
Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.
Signs of soulless writing
- Every sentence has the same length and structure
- No opinions, just neutral reporting
- No acknowledgment of uncertainty or mixed feelings
- No first-person perspective when appropriate
- No humor, no edge, no personality
- Reads like a Wikipedia article or press release
How to add voice
-
Have opinions. Do not just report facts, react to them
- Example: "Part of me thinks this is genius. Another part thinks it's a terrible idea."
-
Vary your rhythm
- Short punchy sentences
- Then longer ones that take their time
-
Acknowledge complexity
- Example: "It works, but it also feels like a workaround more than a real solution."
-
Use "I" when it fits
- Example: "I keep noticing the same issue every time I use it."
-
Let some mess in
- Tangents and asides are human
-
Be specific about feelings
- Not "this is concerning" but something concrete
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.
- 4d ago First seen · 414 lines · 78 tokens per session scan A 3f892e7ab6c9
humanizer is a skill published in the GitHub repository datatorag/mcp-gateway (3 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 2,008 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…