remove-ai-patterns

A writing tool for finding and removing common patterns associated with AI-generated text. It includes checking modes and a bundled catalog of patterns for consistent, offline review.

In plain words
What is it for?
Use it to audit text for AI-style patterns, edit files to remove them, and repeat the review until the text meets the desired standard.
Why use it?
It helps identify wording that can make text sound generic or machine-written. This is useful when you need a repeatable review instead of relying only on personal judgment.

Skill for Claude CodeCodex

Part of the writing plugin — 3 skills shipped together

Install

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.

agentmods
npx agentmods add skills/pchalasani/claude-code-tools/remove-ai-patterns
Any agent
npx skills add pchalasani/claude-code-tools --skill remove-ai-patterns
Clone the repo
git clone --depth 1 https://github.com/pchalasani/claude-code-tools

Made for: Claude Code, Codex.

Or install writing, the plugin that ships this one along with the rest of its 3 skills.

Per session 132 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,362 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00132 $0.01362
Opus 5 $0.00066 $0.00681
Sonnet 5 $0.00026 $0.00272
Haiku 4.5 $0.00013 $0.00136

Measured 3d ago against content hash b7901e75c671, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

remove-ai-patterns 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 3d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/detect.js, upstream/detector/patterns.js, upstream/detector/validate.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/writing/skills/remove-ai-patterns/SKILL.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

remove-ai-patterns

Thin wrapper around Conor Bronsdon's avoid-ai-writing skill (MIT licensed). A pinned snapshot of the upstream catalog and detector is vendored at upstream/ inside this skill directory (commit recorded in upstream/UPSTREAM-PIN), so the skill works offline and deterministically.

How to run

  1. Read upstream/SKILL.md (the full pattern catalog, tiered word lists, and mode definitions) and follow it. It defines the modes: detect-only, edit-in-place for files, optional voice profile, and an iterate-to-convergence pass.

  2. For a deterministic, machine-checkable audit, run the bundled detector (requires Node.js, no npm install needed). Resolve it by the skill's own absolute path, NOT a bare relative path: the command runs from the user's current working directory, so node scripts/detect.js would fail with MODULE_NOT_FOUND. You already know this skill's directory (you just read this SKILL.md from it), so set it once and reuse it. Under a Claude Code plugin install ${CLAUDE_PLUGIN_ROOT} gives the plugin root; under Codex (where that variable is unset) or a direct skill install, substitute the absolute path of the directory holding this file:

    # Claude Code plugin install:
    SKILL_DIR="${CLAUDE_PLUGIN_ROOT}/skills/remove-ai-patterns"
    # Codex plugin or direct skill install: the absolute path of the
    # directory this SKILL.md lives in (it ends in skills/remove-ai-patterns;
    # the plugin root already is the writing plugin, so there is no extra
    # plugins/writing segment). Direct installs are simpler, e.g.
    #   SKILL_DIR="$HOME/.local/share/agent-skills/remove-ai-patterns"
    
    node "$SKILL_DIR/scripts/detect.js" FILE
    

    Pass a context mode as the second argument when the text is technical documentation. In this detector, technical has one concrete effect: it skips the title-case-header check (Title Case section headings are legitimate in technical docs). It does not broadly relax vocabulary checks, and it is not the same as selecting the skill's technical VOICE profile (context and voice are separate axes); the wider technical-prose word exceptions live in the upstream skill's rewrite rules, not in the detector.

Read the full file on GitHub · 112 lines

Files

What ships with it

8 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.

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. 3d ago First seen · 112 lines · 132 tokens per session scan A b7901e75c671

Subscribe to this mod's changes

remove-ai-patterns is a skill published in the GitHub repository pchalasani/claude-code-tools (1,989 stars, last pushed 3d ago), licensed MIT. It adds 132 tokens to every session and 1,362 once invoked, about $0.0007 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.

Related

Other skills, from other repositories

aoe

Use when launching, monitoring, or controlling AI coding agents (Claude Code, Codex, OpenCode, etc.) in tmux via Agent of Empires (aoe). Covers creating sessions, capturing agent output, running parallel worktree agents, and organizing work into groups and profiles. Prefer aoe over raw tmux for agent management.

agent-of-empires/agent-of-empires · 71 tokens

verify-behavior

Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…

nicknisi/dotfiles · 68 tokens

source-drafting

Use when drafting documents, reports, posts, presentations, or review comments from source materials, or conducting research across provided documents. Enforces read-first drafting, a source map for every claim, agent verification, and separation of verified from unverified claims.

nicknisi/dotfiles · 54 tokens

bro

Restate the last message in plain human language, with no jargon.

nicknisi/dotfiles · 16 tokens

luvus-module

Write a luvus module (an extension for luvus, mission control for your AI coding agents). Use when the user is building or debugging a luvus module: authoring luvus-module.toml, adding a sidebar dock, Luvus Bar widget, right-click action, event hook, module pane, module settings, or calling luvus back over its UHP.

RizRiyz/luvus · 79 tokens

new-config

Interactively scaffold a new smug tmux session configuration (a YAML template). Use when the user wants to create, scaffold, or set up a new smug project/config file, or asks for "smug new config", "a smug template", or "/new-config". Walks the user through session name, root, windows, panes, commands, env, and hooks…

ivaaaan/smug · 86 tokens