What is content-audit?

A method for reviewing an existing collection of content, such as blog posts, landing pages, guides, and other resources.

Use it to inventory content, examine analytics, identify search-content overlap, and plan updates based on traffic, leads, conversions, or brand goals.

It helps find outdated, inaccurate, ineffective, or competing content before a redesign, migration, rebrand, or strategy change.

content-audit — Skill for Claude Code by brainbytes-dev

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 brainbytes-dev/everything-claude-marketing --skill content-audit

Clone the repo

git clone --depth 1 https://github.com/brainbytes-dev/everything-claude-marketing

Made for: Claude Code.

Or install everything-claude-marketing, the plugin that ships this one along with the rest of its 72 skills, 22 commands, 18 agents, 2 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/brainbytes-dev/everything-claude-marketing/content-audit/github.svg)](https://agentmods.dev/skills/brainbytes-dev/everything-claude-marketing/content-audit)

Your own site

<a href="https://agentmods.dev/skills/brainbytes-dev/everything-claude-marketing/content-audit"><img src="https://agentmods.dev/badge/skills/brainbytes-dev/everything-claude-marketing/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/brainbytes-dev/everything-claude-marketing/content-audit"><img src="https://agentmods.dev/badge/skills/brainbytes-dev/everything-claude-marketing/content-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,211 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.

Model	Per session	Once invoked
Fable 5.1	$0.00030	$0.02211
Opus 5.5	$0.00012	$0.00884
Sonnet 5.5	$0.00006	$0.00442
Haiku 4.5	$0.00003	$0.00221

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

Security

Grade A, and why

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 2mo 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.

skills/content/content-audit/SKILL.md · 233 lines

How it starts

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

Content Audit

When to Activate

Inheriting a content library from a predecessor or acquisition
Content program has been running for 12+ months without a review
Organic traffic is declining or stagnating
Planning a site redesign, migration, or rebrand that affects content
Suspected content cannibalization (multiple pages competing for the same keyword)
Building a content strategy that needs to account for what already exists
Stakeholders question the ROI of content marketing

First Questions

How many content pieces exist? (Blog posts, landing pages, guides, resources?)
What analytics access do you have? (Google Analytics, Search Console, CMS analytics?)
What is the primary goal of the content program? (Traffic, leads, conversions, brand?)
When was content last reviewed or updated systematically?
How many authors have contributed, and are they still with the organization?
Is there known content that is outdated, inaccurate, or off-brand?
What CMS is used, and can content be bulk-exported for analysis?

Content Inventory Methodology

Step 1: Export Everything

Pull a complete list of published content. For each piece, capture:

URL
Title
Publish date
Last modified date
Author
Content type (blog, guide, case study, landing page, etc.)
Word count
Content pillar/category
Primary keyword (if known)

Sources: CMS export, sitemap.xml (for URL list), Screaming Frog crawl (for metadata), Google Analytics (for performance data), Google Search Console (for search data).

Step 2: Add Performance Data

For each piece, pull metrics for the trailing 12 months:

Metric	Source	Why It Matters
Organic sessions	Google Analytics	Search-driven visibility
Total pageviews	Google Analytics	Overall reach
Avg. time on page	Google Analytics	Engagement depth
Bounce rate	Google Analytics	Content relevance
Conversions/goals	Google Analytics	Business impact
Impressions	Google Search Console	Search visibility
Clicks	Google Search Console	Search traffic
Avg. position	Google Search Console	Ranking performance
Top queries	Google Search Console	What the page ranks for
Backlinks	Ahrefs/SEMrush	Authority and link equity
Social shares	BuzzSumo/native analytics	Social reach

Read the full file on GitHub · 233 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.

2mo ago First seen · 233 lines · 30 tokens per session scan A 7d6e468cc480

Subscribe to this mod's changes

content-audit is a skill published in the GitHub repository brainbytes-dev/everything-claude-marketing (10 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 2,211 once invoked, about $0.0001 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-31.

Marketing and SEO

content-audit next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
content-auditbrainbytes-dev/everything-claude-marketing	Skill	10	7mo ago	MIT	A	30	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code