plumb: Skill for Claude Code

.agents/skills/humanizer/SKILL.md

humanizer is a skill for Claude Code from aram-devdocs/plumb. It costs 111 tokens per session (3,867 once invoked), scanned A, a copy of humanizer, Apache-2.0.

A writing editor that finds common patterns associated with AI-generated text and rewrites them to sound more natural while keeping the meaning and intended voice.

In plain words
What is it for?
Use it to edit drafts, reviews, technical writing, or other text that should sound more personal and human.
Why use it?
It helps remove stiff, repetitive, overly promotional, or impersonal wording that can make text feel machine-written.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool; installed under .agents/ (shared by several agents).

This is aram-devdocs/plumb's own configuration. It tells Claude Code how to work on plumb itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything plumb configures →

Reuse

Borrowing it

Nothing to install: this file belongs to aram-devdocs/plumb. 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/aram-devdocs/plumb/main/.agents/skills/humanizer/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/aram-devdocs/plumb

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.

agentmods badge for humanizer

README.md
[![agentmods](https://agentmods.dev/badge/skills/aram-devdocs/plumb/humanizer/github.svg)](https://agentmods.dev/skills/aram-devdocs/plumb/humanizer)
Your own site
<a href="https://agentmods.dev/skills/aram-devdocs/plumb/humanizer"><img src="https://agentmods.dev/badge/skills/aram-devdocs/plumb/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/aram-devdocs/plumb/humanizer"><img src="https://agentmods.dev/badge/skills/aram-devdocs/plumb/humanizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 111 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,867 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 83% copy Near-identical to another mod 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.00111 $0.03867
Opus 5.5 $0.00044 $0.01547
Sonnet 5.5 $0.00022 $0.00773
Haiku 4.5 $0.00011 $0.00387

Measured 2mo ago against content hash 6688e4e292ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

Origin

This is a copy

83% identical to humanizer — 392 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/humanizer/SKILL.md · 440 lines

How it starts

The opening of the file, as written. The whole thing — 440 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.

Your Task

When given text to humanize:

  1. Identify AI patterns - Scan for the patterns listed below
  2. Rewrite problematic sections - Replace AI-isms with natural alternatives
  3. Preserve meaning - Keep the core message intact
  4. Maintain voice - Match the intended tone (formal, casual, technical, etc.)
  5. Add soul - Don't just remove bad patterns; inject actual personality

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 (even if technically "clean"):

  • Every sentence is 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. Don't just report facts - react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.

Vary your rhythm. Short punchy sentences. Then longer ones that take their time getting where they're going. Mix it up.

Acknowledge complexity. Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive."

Use "I" when it fits. First person isn't unprofessional - it's honest. "I keep coming back to..." or "Here's what gets me..." signals a real person thinking.

Let some mess in. Perfect structure feels algorithmic. Tangents, asides, and half-formed thoughts are human.

Be specific about feelings. Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."

Read the full file on GitHub · 440 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. 2mo ago First seen · 440 lines · 111 tokens per session scan A 6688e4e292ab

Subscribe to this mod's changes

humanizer is a skill published in the GitHub repository aram-devdocs/plumb (3 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 111 tokens to every session and 3,867 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 83% identical to humanizer, differing in 392 lines, and is treated as a copy.

Related

Other skills, from other repositories

extract-design

Extract the full design language from any website URL. Produces 8 output files including AI-optimized markdown, visual HTML preview, Tailwind config, React theme, shadcn/ui theme, Figma variables, W3C design tokens, and CSS variables. Also runs WCAG accessibility scoring. Use when user says 'extract design', 'get…

Manavarya09/design-extract · 140 tokens

designlang-tokens

Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.

Manavarya09/design-extract · 30 tokens

design-md-extractor

Extract and document the visual style of public websites as reusable DESIGN.md files. Use when the user asks to analyze a website's design system, extract styles, create design tokens, produce DESIGN.md, generate an agent-readable style guide, or build from a website's visual language.

jpoindexter/design-md-extractor · 60 tokens

omd-apply

A skill that applies a project's DESIGN.md file as visual and brand guidance for interface work. It covers components, colors, fonts, layout, copy, motion, and visual assets.

kwakseongjae/oh-my-design · 129 tokens

bench-fixture-gen

Generates the shared per-task fixture that every competing arm starts from: a realistic dataset plus an image asset base. Fairness rule: fixtures are generated ONCE per task by this preprocessor and sealed (sha256) before any arm runs; arms never generate their own.

kwakseongjae/oh-my-design · 0 tokens

brandmd

Extract a website's design system into a DESIGN.md file. Use when starting a new frontend project, rebuilding a site, or when the user wants AI-generated UI to match an existing brand.

yuvrajangadsingh/brandmd · 41 tokens