ai-content-audit

ai-content-audit is a skill for Claude Code from mohitagw15856/pm-claude-skills. It costs 137 tokens per session (1,315 once invoked), scanned A, original, MIT.

A review of a collection of articles, documentation or other published content for low-value, repetitive or AI-generated material. It produces decisions about what to keep, improve, rewrite or remove.

In plain words
What is it for?
Use it to audit a blog or documentation site, investigate declining engagement or search visibility, and set standards for future AI-assisted publishing.
Why use it?
It helps find content that sounds fluent but offers little useful information, harms reader trust or performs poorly in search.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the pm-aiwork plugin — 5 skills shipped together

Good fit Use it to audit a blog or documentation site, investigate declining engagement or search visibility, and set standards for future AI-assisted publishing.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mohitagw15856/pm-claude-skills/ai-content-audit
About the project

PM Skills is a collection of plain-Markdown instructions that teach AI assistants structured methods for handling professional, personal, and life-admin tasks. People use it with Claude, ChatGPT, Gemini, Cursor, Codex, and other supported agents for work such as writing product requirements, reviewing documents, or planning difficult situations.

mohitagw15856/pm-claude-skills · 1,449 stars · on GitHub · mohitagw15856.github.io

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 mohitagw15856/pm-claude-skills --skill ai-content-audit
Clone the repo
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills

Made for: Claude Code.

Or install pm-aiwork, the plugin that ships this one along with the rest of its 5 skills.

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 ai-content-audit

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/ai-content-audit"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/ai-content-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 137 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,315 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.
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.00137 $0.01315
Opus 5.5 $0.00055 $0.00526
Sonnet 5.5 $0.00027 $0.00263
Haiku 4.5 $0.00014 $0.00131

Measured 2d ago against content hash e7fb1ed6ed24, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ai-content-audit 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 2d 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.

plugins/pm-aiwork/skills/ai-content-audit/SKILL.md · 83 lines

How it starts

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

AI Content Audit Skill

Teams that scaled content with AI are discovering the bill: libraries full of fluent, structurally identical, information-free pieces that readers bounce off, search engines quietly demote, and — worst — that erode the trust the good content earned. This skill audits the library for slop with named signals, triages it, and installs the gate that stops the refill.

What This Skill Produces

  • An audited inventory with per-piece verdicts: keep / enrich / rewrite / delete-and-redirect
  • The detection signals found, quoted — so verdicts are checkable, not vibes
  • A triage plan sequenced by traffic and trust impact
  • A publishing quality gate for AI-assisted content going forward

Required Inputs

Ask for (if not already provided):

  • The corpus — pieces or URLs to audit (or a sample; state the sampling), with publish dates
  • Performance data if available — traffic, engagement, rankings over time (the audit works without it, but verdicts get sharper)
  • What the content is for — SEO, docs, thought leadership, support deflection (the quality bar differs)
  • Production context — when AI-assisted publishing started, at what volume (the before/after seam is diagnostic gold)

Detection Method

Slop isn't "AI wrote it" — it's content with nothing inside. Audit each piece for the signals, quoting instances:

  1. Information density — the core test: delete every sentence that any competitor could have written, and measure what's left. Slop survives at <20%. Look for: zero proprietary data, zero named examples, zero opinions with an owner, zero specifics a reader could act on.
  2. Structural monoculture — the same skeleton repeating across pieces (intro-restating-the-title → 5 H2s → "in conclusion"); listicles whose items are definitions, not judgments; FAQ sections answering questions nobody asked.
  3. Hedged voicelessness — "it's important to note", "in today's fast-paced world", both-sides-ism on questions the brand should have a stance on; the absence of anything a lawyer would ever have flagged.
  4. Fluency without grounding — claims with no source, stats with no year, "studies show" with no study; internally contradictory sections (the tell of stitched generations).
  5. Reader evidence, where data exists — engagement collapse relative to the library's pre-AI baseline, rising pogo-sticking, ranking decay cohort-matched to the AI-volume era. Correlate verdicts with the seam from the production context.

Read the full file on GitHub · 83 lines

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. 2d ago First seen · 83 lines · 137 tokens per session scan A e7fb1ed6ed24

Subscribe to this mod's changes

ai-content-audit is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 137 tokens to every session and 1,315 once invoked, about $0.0005 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-10-12.

Related

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…

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

systematic-debugging

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

obra/superpowers · 21 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