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 skills add betahope/cofounder-team --skill humanizergit clone --depth 1 https://github.com/betahope/cofounder-teamWrote 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/betahope/cofounder-team/humanizer)<a href="https://agentmods.dev/skills/betahope/cofounder-team/humanizer"><img src="https://agentmods.dev/badge/skills/betahope/cofounder-team/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.
<a href="https://agentmods.dev/skills/betahope/cofounder-team/humanizer"><img src="https://agentmods.dev/badge/skills/betahope/cofounder-team/humanizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00194 | $0.02555 |
| Opus 5 | $0.00097 | $0.01277 |
| Sonnet 5 | $0.00039 | $0.00511 |
| Haiku 4.5 | $0.00019 | $0.00255 |
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 9d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Humanizer
Takes AI-sounding writing and makes it sound like a person wrote it. Grounded in Wikipedia's Signs of AI writing guide, maintained by WikiProject AI Cleanup.
Key insight from that page: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases." That's why AI writing feels smoothed-over and genericized: the model is producing the statistical average of what a sentence looks like. Humanizing means putting specificity, rhythm, and a point of view back in.
How this skill is organized
The pattern catalog is not ours. It comes from blader/humanizer, MIT licensed, and is vendored here unchanged so it stays current without anyone re-typing it.
- This file: the workflow, the language rule, output sizing, and the voice guidance.
references/upstream-patterns.md: the full pattern catalog, straight from upstream. Every pattern has a words-to-watch list, the underlying problem, a before/after example, and notes on what not to flag.references/voice-calibration.md: how to match a user's writing sample.references/example.md: a long-form before/after at full-essay scale.
Read references/upstream-patterns.md on every real humanizing pass. It is the
authority on which patterns exist and how to fix each one. This file is the authority
on workflow, output length, language scope, and voice. Where the two disagree, this
file wins.
The patterns group into five families: content (what AI over-claims), language and grammar (how it phrases things), style (surface formatting tells), chatbot leakage (register left over from the assistant), and filler and hedging (padding). Deliberately no numbered index here: upstream adds and renumbers patterns, and a second list would drift out of sync with the first.
Scope: full pass in English, structural pass in any language
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.
- 9d ago First seen · 211 lines · 194 tokens per session scan A 46f2ed3ae10c
humanizer is a skill published in the GitHub repository betahope/cofounder-team (27 stars, last pushed 2d ago), licensed MIT. It adds 194 tokens to every session and 2,555 once invoked, about $0.0010 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…