content-optimizer

An on-page search-engine-optimization checker and writing guide. Search-engine optimization means improving a web page so search engines can understand and rank it; this tool checks keywords, page descriptions, headings, URLs, and readability.

In plain words
What is it for?
Use it to improve existing web pages or review new ones before publishing. It helps create titles, descriptions, URLs, headings, and readable copy that follow stated SEO requirements.
Why use it?
It helps find content and page-structure issues that can make a page harder to understand for readers or search engines. It also provides checks for keyword use and metadata.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/nicepkg/ai-workflow/content-optimizer
Any agent
npx skills add nicepkg/ai-workflow --skill content-optimizer
Clone the repo
git clone --depth 1 https://github.com/nicepkg/ai-workflow

Made for: Claude Code, Codex.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 752 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00035 $0.00752
Opus 5 $0.00017 $0.00376
Sonnet 5 $0.00007 $0.00150
Haiku 4.5 $0.00003 $0.00075

Measured 2d ago against content hash b155cace876d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

content-optimizer 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.

workflows/marketing-pro-workflow/.claude/skills/content-optimizer/SKILL.md · 113 lines

How it starts

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

Content Optimizer

When to Use

  • Optimizing existing content for better rankings
  • Validating new content against SEO requirements
  • Checking keyword density and placement
  • Improving readability scores
  • Creating meta tags

Keyword Density

Target: 1-2% for primary keyword

Calculation:

Density = (Keyword Count / Total Words) x 100

Placement Priorities:

  1. Title/H1 (required)
  2. First 100 words (required)
  3. At least one H2 (recommended)
  4. Conclusion (recommended)
  5. Distributed in body (natural)

Warning Signs:

  • 3% = Keyword stuffing risk

  • <0.5% = Under-optimized
  • Exact match every paragraph = Unnatural

Meta Tag Optimization

Title Tag

  • Length: 50-60 characters
  • Keyword: Near the beginning
  • Format: {Keyword} - {Benefit} | {Brand}
  • Unique per page

Meta Description

  • Length: 150-160 characters
  • Keyword: Include naturally
  • CTA: End with action verb
  • Unique per page

URL Slug

  • Short: 3-5 words
  • Keyword: Include primary
  • Readable: Use hyphens
  • Lowercase only

Heading Structure

Valid Hierarchy:

H1: Page Title (exactly 1)
+-- H2: Main Section
|   +-- H3: Subsection
|   +-- H3: Subsection
+-- H2: Main Section
|   +-- H3: Subsection
+-- H2: Conclusion

Common Errors:

  • Multiple H1 tags
  • Skipping levels (H1 -> H3)
  • Using headings for styling only
  • No keyword in H1

Readability Optimization

Flesch Reading Ease Target: 60-70

Score Level Audience
90-100 Very Easy 5th grade
80-89 Easy 6th grade
70-79 Fairly Easy 7th grade
60-69 Standard 8th-9th grade
50-59 Fairly Difficult 10th-12th grade
30-49 Difficult College
0-29 Very Difficult College graduate

Improvement Techniques:

  • Shorten sentences (<20 words avg)
  • Shorten paragraphs (2-3 sentences)
  • Replace jargon with plain language
  • Use active voice
  • Add subheadings every 200-300 words
  • Use bullet points for lists

Optimization Checklist

Read the full file on GitHub · 113 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. 2d ago First seen · 113 lines · 35 tokens per session scan A b155cace876d

Subscribe to this mod's changes

content-optimizer is a skill published in the GitHub repository nicepkg/ai-workflow (282 stars, last pushed 7mo ago), licensed MIT. It adds 35 tokens to every session and 752 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-30.