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 nicepkg/ai-workflow --skill content-optimizergit clone --depth 1 https://github.com/nicepkg/ai-workflowWrote 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/nicepkg/ai-workflow/content-optimizer)<a href="https://agentmods.dev/skills/nicepkg/ai-workflow/content-optimizer"><img src="https://agentmods.dev/badge/skills/nicepkg/ai-workflow/content-optimizer/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/nicepkg/ai-workflow/content-optimizer"><img src="https://agentmods.dev/badge/skills/nicepkg/ai-workflow/content-optimizer.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.00035 | $0.00752 |
| Opus 5.5 | $0.00014 | $0.00301 |
| Sonnet 5.5 | $0.00007 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
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 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.
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:
- Title/H1 (required)
- First 100 words (required)
- At least one H2 (recommended)
- Conclusion (recommended)
- 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
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.
- 1mo ago First seen · 113 lines · 35 tokens per session scan A b155cace876d
content-optimizer is a skill published in the GitHub repository nicepkg/ai-workflow (286 stars, last pushed 8mo ago), licensed MIT. It adds 35 tokens to every session and 752 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for saveplan, outputiframe, or slackattachhtml.
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
hive.pdf
Read, write, merge, split, rotate, watermark, encrypt, and OCR PDF files using Python (pypdf, pdfplumber, reportlab, pypdfium2) and command-line tools (poppler-utils, qpdf). Use when the user asks to extract text/tables/images from a PDF, create or modify a PDF, combine or split PDFs, OCR a scanned PDF…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.