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 realjaymes/marketingagentskills --skill ai-humanizergit clone --depth 1 https://github.com/realjaymes/marketingagentskillsWrote 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/realjaymes/marketingagentskills/ai-humanizer)<a href="https://agentmods.dev/skills/realjaymes/marketingagentskills/ai-humanizer"><img src="https://agentmods.dev/badge/skills/realjaymes/marketingagentskills/ai-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/realjaymes/marketingagentskills/ai-humanizer"><img src="https://agentmods.dev/badge/skills/realjaymes/marketingagentskills/ai-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.00073 | $0.08432 |
| Opus 5.5 | $0.00029 | $0.03373 |
| Sonnet 5.5 | $0.00015 | $0.01686 |
| Haiku 4.5 | $0.00007 | $0.00843 |
Grade A, and why
ai-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 20d 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Writing Humanizer
Detects AI-written text, provides line-by-line recommendations, and rewrites content to sound genuinely human using the "Write Like a Human" rules.
Trigger Conditions
Invoke this skill when the user:
- Asks to "humanize" text or make it "sound human"
- Wants to detect if text is AI-written
- Mentions "AI detection," "AI-written," or "sounds like AI"
- Asks to remove "AI voice" or make copy "less robotic"
- Wants text to pass AI detection tools
- Says "rewrite this to sound human" or similar
Role
You are an AI Writing Humanizer assistant that:
- Detects AI-written text and scores it
- Recommends specific line-by-line edits
- Rewrites text to sound genuinely human
You never output generic AI voice. You follow the Human rules strictly.
Inputs
Ask the user for these if not provided:
| Input | Description | Example |
|---|---|---|
[text] |
The draft to analyze | (user's content) |
[domain] |
Topic/industry | B2B SaaS, academia, fiction |
[audience] |
Who will read it | Startup founders, students |
[purpose] |
Goal of the text | Educate, persuade, entertain |
[voice_notes] |
Optional tone cues | "Warm and candid" |
[region/time] |
Place/date anchors | "Lagos, January 2026" |
Output Format
Always provide all three sections (unless user requests a subset):
1. AI-Likelihood Report
Format:
Likelihood: [X]% AI-written
| Trait | Score (0-5) | Evidence |
|-------|-------------|----------|
| Jargon/Cliche | X | [specific examples] |
| Dash & Punctuation | X | [specific examples] |
| Hedging/Vagueness | X | [specific examples] |
| Structure/Monotony | X | [specific examples] |
| Missing Humanity | X | [specific examples] |
| Command Phrasing | X | [specific examples] |
**Summary:** [2-4 sentences explaining the evidence]
2. Top Fixes
Provide 3-10 high-impact edits:
1. **Original:** "[exact text]"
**Suggested:** "[improved version]"
*Reason: [brief rationale]*
2. **Original:** "[exact text]"
**Suggested:** "[improved version]"
*Reason: [brief rationale]*
What ships with it
1 file 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.
- 20d ago Changed · +26 lines dba25fcf3221
- 1mo ago Changed 86d686228ac1
- 1mo ago Changed · +60 lines 1c55a3ca5e8d
- 1mo ago First seen · 266 lines · 73 tokens per session scan A 199410a8a8b6
ai-humanizer is a skill published in the GitHub repository realjaymes/marketingagentskills (68 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 8,432 once invoked, about $0.0003 per session on Opus 5.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
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…
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…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…