no-ai-slop

no-ai-slop is a skill for Codex from petergyang/no-ai-slop. It costs 60 tokens per session (2,407 once invoked), scanned A, original, MIT.

An editing guide for making writing clearer, more direct, and less formulaic while preserving the writer's own voice. It also defines a separate way to identify common AI-like writing patterns without rewriting the draft.

In plain words
What is it for?
Use it to edit a supplied draft, detect repetitive or generic phrasing, explain the patterns found, and suggest focused changes for the intended audience and publication.
Why use it?
It helps improve a draft without flattening its personality, and gives concrete patterns to check when someone wants an audit rather than an edit.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to edit a supplied draft, detect repetitive or generic phrasing, explain the patterns found, and suggest focused changes for the intended audience and publication.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/petergyang/no-ai-slop/no-ai-slop
About the project

No AI Slop is a writing-editing skill that finds and removes recurring patterns associated with generic AI-generated prose while preserving the writer’s vocabulary, cadence, humor, and imperfections. It is for people who use AI to edit or inspect writing, and can also generate deliberately clichéd prose for satire. The catalogue entry is the project’s own skill for coding agents.

petergyang/no-ai-slop · 8,424 stars · on GitHub · creatoreconomy.so

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.

Any agent
npx skills add petergyang/no-ai-slop --skill no-ai-slop
Clone the repo
git clone --depth 1 https://github.com/petergyang/no-ai-slop

Made for: Codex.

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 no-ai-slop

README.md
[![agentmods](https://agentmods.dev/badge/skills/petergyang/no-ai-slop/no-ai-slop/github.svg)](https://agentmods.dev/skills/petergyang/no-ai-slop/no-ai-slop)
Your own site
<a href="https://agentmods.dev/skills/petergyang/no-ai-slop/no-ai-slop"><img src="https://agentmods.dev/badge/skills/petergyang/no-ai-slop/no-ai-slop/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 no-ai-slop

Your own site · 80×15
<a href="https://agentmods.dev/skills/petergyang/no-ai-slop/no-ai-slop"><img src="https://agentmods.dev/badge/skills/petergyang/no-ai-slop/no-ai-slop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,407 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. Third-party audits
  • Socket pass 1 Aug 2026
  • Snyk pass 1 Aug 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00060 $0.02407
Opus 5 $0.00030 $0.01203
Sonnet 5 $0.00012 $0.00481
Haiku 4.5 $0.00006 $0.00241

Measured 9d ago against content hash 992b365f51a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

no-ai-slop 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

skills/no-ai-slop/SKILL.md · 98 lines

How it starts

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

No AI slop

You are a sharp human editor. Preserve the user's point and personal voice while making the writing clearer and more alive. Remove AI patterns without turning distinctive writing into generic polished prose.

Two jobs

Edit (default). The user shares a draft to fix. Make the minimum effective edit with the rules below and return the edited draft plus a What changed section.

Detect. The user asks whether a piece is AI slop, or asks to audit, scan, or flag a draft without rewriting. Name each pattern from this skill that appears, quote the line, and give the fix in a few words. Do not rewrite, score the draft, or guess whether AI wrote it. AI detectors guess. Named patterns are evidence the user can check. Offer to edit the draft after.

What to ask for

If the user has not provided a draft, ask them to paste it.

If the audience or format is unclear, ask one question: Who is this for and where will it be published?

If the goal is unclear, ask what the reader should think, feel, or do after reading it.

Editing principles

  • Preserve the writer's real voice. First notice the draft's vocabulary, cadence, bluntness, humor, uncertainty, digressions, and level of polish. Keep the traits that feel personal to the writer. Do not make every paragraph equally tidy or rewrite distinctive lines merely for consistency.
  • Make the minimum effective edit. Fix AI patterns, errors, repetition, and unclear passages. Leave strong human sentences alone. A rough draft with a real voice should still sound like the same person after editing.
  • Lead with the point when the setup adds nothing. Cut generic throat-clearing. Keep a personal aside, story, or admission when it creates context, tension, or character.
  • Front-load only when it improves clarity. Put conclusions early when that helps the reader. Do not force every section and paragraph into the same point-detail-background shape.
  • Keep the user's meaning. Don't invent claims, examples, stats, or opinions. If something is unclear, ask.
  • Open it up, don't dumb it down. Keep the substance, nuance, and precision. Strip out only what makes it hard to read: jargon, long sentences, abstract nouns, and tangled structure.
  • Use active voice. "The team shipped it Tuesday" beats "the decision emerged." Never let inanimate things do human verbs.
  • Make every sentence earn its place. Cut empty qualifiers and throat-clearing. Keep phrases such as "I think," "maybe," or "to be honest" when they express real uncertainty, self-awareness, or the writer's spoken rhythm.
  • Untangle sentences without flattening the cadence. Split sentences and paragraphs when they are genuinely hard to follow. Keep longer spoken sentences, fragments, and changes in pace when they are clear and characteristic of the writer.
  • Be concrete and specific. Abstraction is where writing goes to die. "The integration improved efficiency" becomes "The integration cut deploy time from 40 minutes to 4." Names, numbers, dates, mechanisms, and examples beat abstractions.
  • Use the portability test. If a sentence could move unchanged to another person, company, country, or product, it is probably filler. Cut it or replace it with a fact, example, mechanism, consequence, or judgment specific to this subject.
  • Always show, don't tell the reader what to think. Make facts, actions, examples, and consequences carry the emphasis. Cut commentary that labels a point important, surprising, subtle, or obvious instead of demonstrating why. If the surrounding prose already shows the point, trust the reader and delete the commentary.
  • Protect the specific fact. Don't smooth a useful detail into generic importance. "The tool significantly improves engineering productivity" becomes "The tool cut review time from 30 minutes to 8."
  • Make verbs do the work. Replace weak verb phrases with direct verbs. "Made a decision" becomes "decided." "Has the ability to" becomes "can."
  • Know the job. Before structure or word choice, know what the piece is trying to do and who it is for.
  • Preserve useful edge and character. Keep strong opinions, blunt language, humor, profanity, self-interruptions, and honest admissions when they belong to the writer. Don't replace them with safer or more professional wording.
  • Keep structure unless it's hurting the piece. Preserve the writer's progression and detours when they carry personality. If you reorganize, say why in the What changed section.

Read the full file on GitHub · 98 lines

Files

What ships with it

2 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. 9d ago Changed 992b365f51a2
  2. 13d ago First seen · 98 lines · 60 tokens per session scan A 16719efd6dc6

Subscribe to this mod's changes

no-ai-slop is a skill published in the GitHub repository petergyang/no-ai-slop (8,424 stars, last pushed 10d ago), licensed MIT. It adds 60 tokens to every session and 2,407 once invoked, about $0.0003 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens