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 skills add arturseo-geo/claude-code-skills --skill content-auditgit clone --depth 1 https://github.com/arturseo-geo/claude-code-skillsWrote 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/arturseo-geo/claude-code-skills/content-audit)<a href="https://agentmods.dev/skills/arturseo-geo/claude-code-skills/content-audit"><img src="https://agentmods.dev/badge/skills/arturseo-geo/claude-code-skills/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.
<a href="https://agentmods.dev/skills/arturseo-geo/claude-code-skills/content-audit"><img src="https://agentmods.dev/badge/skills/arturseo-geo/claude-code-skills/content-audit.svg" alt="Reviewed on agentmods" width="80" 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.00128 | $0.01177 |
| Opus 5 | $0.00064 | $0.00589 |
| Sonnet 5 | $0.00026 | $0.00235 |
| Haiku 4.5 | $0.00013 | $0.00118 |
Grade B, and why
content-audit scanned grade B with 2 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 10d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Clear nginx cache before auditing: `rm -rf /var/cache/nginx/fastcgi/* && systemctl reload nginx` Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Always check the RENDERED page (via curl or browser), not just post_content How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Audit Skill
Post-publication maintenance for AI search visibility. This skill audits published content for GEO compliance, detects freshness decay, tests LLM readability at the section level, and manages re-test schedules.
Lifecycle position: seo-geo (plan) → content-pipeline (create) → content-audit (maintain)
Reference Files — Load When Relevant
| Topic | File | Load when... |
|---|---|---|
| GEO compliance checklist | references/compliance-checklist.md |
Auditing pages for schema, structure, voice, CTAs |
| GEO Quality Gate | references/geo-quality-gate.md |
Per-section quality review (5 questions) |
| Content freshness | references/content-freshness.md |
Detecting stale statistics, planning updates |
| LLM readability | references/llm-readability.md |
Testing sections for passage-level AI processability |
| Re-test cadence | references/retest-cadence.md |
Scheduling and triggering citation rate re-tests |
When This Skill Triggers
- "audit this page for GEO compliance"
- "check if the content is still fresh"
- "test the LLM readability of this section"
- "when should I re-test citation rates?"
- "is this section citation-ready?"
- "run a content maintenance check"
- "check for stale statistics"
- "are the opening sentences declarative enough?"
Core Workflow
1. Full Page Audit
When asked to audit a page, run all checks from references/compliance-checklist.md:
- Schema (Article + FAQPage + Organization + Review JSON-LD)
- Structure (single H1, TL;DR, FAQ, TOC, figure, key takeaways)
- Voice (first-person ≥2, "since 2004" in bio, no self-review)
- Links (internal ≥4, external ≥2, no homepage links)
- CTAs (closing CTA + ebook callout)
- Report PASS/FAIL per check with counts
2. Section-Level Quality Gate
When asked to review content quality, run all 5 questions from
references/geo-quality-gate.md on every H2 section:
- Direct declarative opener?
- All pronouns resolved?
- Single topic per section?
- Verifiable data point present?
- Citation-ready opening sentence?
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 131 lines · 128 tokens per session scan B 19a516fd506d
content-audit is a skill published in the GitHub repository arturseo-geo/claude-code-skills (11 stars, last pushed 5mo ago), licensed MIT. It adds 128 tokens to every session and 1,177 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
security-compliance
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.
cache-components
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). PROACTIVE ACTIVATION: Use this skill automatically when working in Next.js projects that have cacheComponents: true in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best…
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.
stride-analysis-patterns
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
blind-spot-pass
Use before starting work in a domain you don't know well, to surface the "unknown unknowns" — the things you don't even know to ask about — and learn just enough to prompt and decide well. Implements the "blind spot pass" pattern from Anthropic's Fable "finding your unknowns" field guide. Triggers when you say "I'm…
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.