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/cenconq25/claude-code-app-studio/content-auditnpx skills add cenconq25/claude-code-app-studio --skill content-auditgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/content-audit)<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="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.1 | $0.00049 | $0.01798 |
| Opus 5 | $0.00024 | $0.00899 |
| Sonnet 5 | $0.00010 | $0.00360 |
| Haiku 4.5 | $0.00005 | $0.00180 |
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 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.
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/TSlib/for Flutterios/and Xcode project for iOS nativeapp/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 inapp/(Expo Router) - Onboarding screens: count screens under
src/screens/onboarding/or matching pattern - Locales: list files under
src/locales/,src/i18n/, orassets/locales/ - Asset images: count under
assets/images/andsrc/assets/ - Components: count under
src/components/
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.
- 2d ago First seen · 217 lines · 49 tokens per session scan A b6f809ed9aea
content-audit is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 1,798 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…