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 skills/brainbytes-dev/everything-claude-marketing/content-auditnpx skills add brainbytes-dev/everything-claude-marketing --skill content-auditgit clone --depth 1 https://github.com/brainbytes-dev/everything-claude-marketingWrote 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/skills/brainbytes-dev/everything-claude-marketing/content-audit)<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="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 | $0.00030 | $0.02211 |
| Opus 5 | $0.00015 | $0.01105 |
| Sonnet 5 | $0.00006 | $0.00442 |
| Haiku 4.5 | $0.00003 | $0.00221 |
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 4d 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 — 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 |
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.
- 4d ago First seen · 233 lines · 30 tokens per session scan A 7d6e468cc480
content-audit is a skill published in the GitHub repository brainbytes-dev/everything-claude-marketing (5 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 2,211 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…