content-audit

content-audit is a skill for Claude Code from cenconq25/claude-code-app-studio. It costs 49 tokens per session (1,798 once invoked), scanned A, original, MIT.

A read-only check that compares content promised in product requirements documents with content present in the codebase. It checks counts and presence for items such as screens, text, images, languages, notifications, and onboarding steps.

In plain words
What is it for?
Use it to audit content-heavy features, verify translations and copy changes, and confirm that planned app screens and onboarding steps exist.
Why use it?
It shows what is planned versus what is actually built, helping catch missing content before release or during development.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

Good fit Use it to audit content-heavy features, verify translations and copy changes, and confirm that planned app screens and onboarding steps exist.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cenconq25/claude-code-app-studio/content-audit
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 cenconq25/claude-code-app-studio --skill content-audit
Clone the repo
git clone --depth 1 https://github.com/cenconq25/claude-code-app-studio

Made for: Claude Code.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/content-audit"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/content-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,798 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.00049 $0.01798
Opus 5.5 $0.00020 $0.00719
Sonnet 5.5 $0.00010 $0.00360
Haiku 4.5 $0.00005 $0.00180

Measured 1mo ago against content hash b6f809ed9aea, 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 1mo 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.

.claude/skills/content-audit/SKILL.md · 217 lines

How it starts

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

Content Audit

A PRD says "5 onboarding screens"; the codebase has 3. A PRD says "supported locales: en, es, ja"; the i18n bundle has only en.json. This skill quantifies that gap.

Read-only. Produces a printed report.


Purpose / When to Run

Run when:

  • Pre-release — confirm content matches plan before submitting to stores
  • Mid-sprint — confirm a content-heavy feature is on track
  • After a copy push — confirm strings landed
  • The user types "content audit" or wants a quick "is the content done" check

Distinct from /asset-audit (in the second skill set, which checks assets specifically) — this skill checks counts and presence, not asset compliance.

Inputs

  • All design/prd/*.md
  • Source code:
    • src/ for RN/JS/TS
    • lib/ for Flutter
    • ios/ and Xcode project for iOS native
    • app/src/main/ for Android native
  • Localization bundles
  • Asset directories (assets/, Assets.xcassets, app/src/main/res/)

Outputs

  • A printed report. No file writes.

Phase 1: Inventory Planned Counts

Read every PRD. From each, extract count claims. Common patterns to grep:

  • " screens"
  • " onboarding steps"
  • "supported locales: "
  • "push categories: "
  • " illustrations"
  • " default templates"
  • "feature flags: "
  • "tabs: "

Build a planned-content table:

| Source PRD | Item | Planned count |
|------------|------|----------------|
| onboarding.md | screens | 5 |
| onboarding.md | locales | en, es, ja |
| paywall.md | tiers | 3 (monthly, annual, lifetime) |
| home.md | tabs | 4 |
| ... | ... | ... |

If a PRD makes vague claims ("a few", "several"), warn but do not error. List them as unknown and recommend tightening the PRD.


Phase 2: Inventory Implemented Counts

Use globs and greps appropriate to the framework. The skill must be framework-aware — read .claude/docs/technical-preferences.md first.

React Native / Expo

  • Screens: glob src/screens/**/*.{tsx,jsx} or routes in app/ (Expo Router)
  • Onboarding screens: count screens under src/screens/onboarding/ or matching pattern
  • Locales: list files under src/locales/, src/i18n/, or assets/locales/
  • Asset images: count under assets/images/ and src/assets/
  • Components: count under src/components/

Read the full file on GitHub · 217 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. 1mo ago First seen · 217 lines · 49 tokens per session scan A b6f809ed9aea

Subscribe to this mod's changes

content-audit is a skill published in the GitHub repository cenconq25/claude-code-app-studio (42 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 1,798 once invoked, about $0.0002 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-09-03.