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 instructions/johnakande/ai-humanizer-skill/agents-mdgit clone --depth 1 https://github.com/johnakande/AI-Humanizer-SkillWrote 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/instructions/johnakande/ai-humanizer-skill/agents-md)<a href="https://agentmods.dev/instructions/johnakande/ai-humanizer-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/johnakande/ai-humanizer-skill/agents-md.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.1 | $0.01090 | $0.01090 |
| Opus 5 | $0.00545 | $0.00545 |
| Sonnet 5 | $0.00218 | $0.00218 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
AI-Humanizer-Skill AGENTS.md 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 5d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI coding agents (Claude Code, Codex, Warp, etc.) working in this repository.
What this repo is
A Claude Code / OpenCode skill implemented entirely as Markdown. The runtime artifact is SKILL.md: the agent reads its YAML frontmatter (metadata) followed by the editor prompt. There is no build step for the skill itself; the only code in this repo is the validation script under scripts/.
This skill is intentionally separate from humanizer. Do not merge them, and do not add cross-repo dependencies. If a change belongs in humanizer's general AI-pattern detection instead of this skill's house style, it goes in that repo, not this one.
Key files
SKILL.md— the skill itself. YAML frontmatter (name,description,license,metadata.version) followed by the rule set: sentence rules, word rules, structure rules, tone rules, 13 numbered patterns with before/after examples, a "what not to flag" guardrail section, and voice calibration. This is the source of truth.README.md— for humans: installation, usage, the output contract, the pattern tables, a full worked example, and a version history..claude-plugin/plugin.json— Claude Code plugin manifest. Pointsskillsat./(the repo root, whereSKILL.mdlives)..claude-plugin/marketplace.json— makes the repo installable via/plugin marketplace add johnakande/ai-humanizer-skill.scripts/validate-package.py— checks thatSKILL.md,README.md, andplugin.jsonhaven't drifted apart. No external dependencies..github/workflows/validate.yml— runs the validator, a skill-discovery check, and a Claude plugin check on every push and pull request.
The maintenance contract
SKILL.md, README.md, and the two .claude-plugin/*.json files must stay in sync. When you change behavior or content:
- Patterns: the skill currently defines 13 numbered patterns under "Patterns to catch," headed
### 1.through### 13.. If you add, remove, or renumber any, update the README pattern tables, the "N patterns" references, andscripts/validate-package.py's expected range in the same change. - Banned words: the word list in the "Word rules" section is a single flat list, not numbered. If you add or remove entries, keep the list alphabetized-by-convenience (grouped loosely by theme is fine) and don't duplicate an entry that's already covered by a different phrasing.
- Version: version lives in
SKILL.md'smetadata.versionfrontmatter field,.claude-plugin/plugin.json'sversionfield, and README's first "Version History" entry. Bump all three together. Do not add a top-levelversion:field toSKILL.md(it belongs undermetadata:), and do not addcompatibility:orallowed-tools:fields. The validator rejects both. - Output contract: for pasted text, "deliver final text only, no draft, no summary" is the defining difference from humanizer's default (which shows a draft/audit/final loop on request). File mode is the one exception, where a short after-the-fact summary is expected because the rewrite itself isn't visible inline. Don't soften the pasted-text default without the user's explicit sign-off, since it was a deliberate, repeated instruction, not a default this repo drifted into.
- Non-obvious fixes: if you change the prompt to handle a tricky failure mode (a rule that kept getting missed, an edge case in the cut list), add a short note to the README version history explaining what was fixed and why.
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.
- 5d ago First seen · 51 lines · 1,090 tokens per session scan A d285b8da60bd
AI-Humanizer-Skill AGENTS.md is an instructions file published in the GitHub repository johnakande/AI-Humanizer-Skill (11 stars, last pushed 15d ago), licensed MIT. It adds 1,090 tokens to every session, about $0.0054 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).