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.
/plugin marketplace add Aboudjem/humanizer-skillnpx agentmods add plugins/aboudjem/humanizer-skill/humanizer-skillgit clone --depth 1 https://github.com/Aboudjem/humanizer-skillGrade 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 2d 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.
What it actually says
{
"name": "humanizer",
"version": "0.6.2",
"description": "Detects 55 AI writing patterns and rewrites text in five voice profiles so it reads like a specific human wrote it, with an optional 0-100 AI-tell score. Use when text sounds AI-generated or like a chatbot, when preparing a blog post, README, or LinkedIn post for publication, when auditing prose for AI tells, or when editing a Markdown file in place. Triggers on phrases like \"humanize this\", \"make this sound less AI\", \"make this sound human\", \"remove AI tells\", \"does this read like ChatGPT\", and \"rewrite so it does not sound AI-generated\". Pure Markdown, zero dependencies, no network calls.",
"author": {
"name": "Adam Boudjemaa",
"email": "[email protected]"
},
"license": "MIT",
"keywords": [
"claude-code",
"claude-code-plugin",
"humanizer",
"ai-writing",
"writing-tools",
"ai-detection",
"burstiness",
"voice-profiles",
"text-rewriting",
"content-quality"
],
"skills": "./skills/"
}
What ships with it
1 file beside plugin.json 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.
- 2d ago First seen · 24 lines scan A 97cf7a0067a8
humanizer is a plugin published in the GitHub repository Aboudjem/humanizer-skill (206 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.
Other plugins, from other repositories
patina
patina — a deterministic, auditable AI-writing humanizer for Korean, English, Chinese, and Japanese.
patina
Detect and rewrite AI writing patterns in Korean, English, Chinese, and Japanese so text reads as if a human wrote it. Meaning-preservation (MPS) verified, audit-friendly. The root SKILL.md is loaded as the /patina skill.
signs-of-ai
Install Signs of AI Writing as a Claude Code plugin.
signs-of-ai
Measure a text for the signs of AI writing and read back the evidence — offline, EN/ES, with the tool's own false-positive rate attached.
untell
untell — an AI-detector auditing toolkit for Claude Code (detector-in-the-loop measurement).
untell
Humanize AI-generated text via a closed-loop, detector-feedback rewrite. Optimizes against GPTZero, ZeroGPT, Originality.ai and other Turnitin-class checkers while preserving meaning, citations and facts. Research/defensive tool.