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 schwepps/skills --skill seo-content-auditgit clone --depth 1 https://github.com/schwepps/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/schwepps/skills/seo-content-audit)<a href="https://agentmods.dev/skills/schwepps/skills/seo-content-audit"><img src="https://agentmods.dev/badge/skills/schwepps/skills/seo-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/schwepps/skills/seo-content-audit"><img src="https://agentmods.dev/badge/skills/schwepps/skills/seo-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.00058 | $0.02205 |
| Opus 5 | $0.00029 | $0.01103 |
| Sonnet 5 | $0.00012 | $0.00441 |
| Haiku 4.5 | $0.00006 | $0.00220 |
Grade A, and why
seo-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 9d 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 — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Content Audit Framework
Professional methodology for comprehensive on-page SEO and content quality analysis.
When to Use This Skill
- Auditing existing content for SEO performance
- Reviewing new content before publication
- Identifying optimization opportunities
- Evaluating E-E-A-T signals
- Scoring content quality
- Competitive content analysis
- Creating content improvement plans
Audit Workflow
Phase 1: On-Page SEO Elements
Title Tag Analysis:
□ Length: 50-60 characters
□ Primary keyword near beginning (first 30 chars)
□ Unique across site
□ Compelling for CTR
□ Brand included (if space)
□ No keyword stuffing
□ Matches search intent
Meta Description Analysis:
□ Length: 150-160 characters
□ Contains primary keyword
□ Includes call-to-action
□ Unique across site
□ Accurately describes content
□ Compelling for clicks
Header Structure (H1-H6):
Requirements:
□ Single H1 matching topic
□ H1 contains primary keyword
□ Logical hierarchy (H1 → H2 → H3)
□ No skipped levels
□ Keywords in H2s naturally
□ Descriptive, not generic
URL Structure:
□ Clean, descriptive
□ Contains primary keyword
□ Under 60 characters
□ Lowercase with hyphens
□ No parameters or IDs
□ Matches content hierarchy
Phase 2: Content Quality Assessment
Content Completeness Scoring:
| Factor | Check | Score |
|---|---|---|
| Topic coverage | Comprehensive vs. shallow | /10 |
| Unique value | Original insights vs. rehash | /10 |
| Accuracy | Factual, verifiable | /10 |
| Freshness | Current information | /10 |
| Depth | Expert-level detail | /10 |
The C.R.E.A.T.E. Framework:
| Factor | Question | Score 1-4 |
|---|---|---|
| Comprehensiveness | Does it fully answer the query? | |
| Relevance | Does it match search intent? | |
| Expertise | Does it demonstrate deep knowledge? | |
| Actionability | Can readers apply this immediately? | |
| Trustworthiness | Are claims supported by evidence? | |
| Engagement | Is it interesting to read? |
What ships with it
3 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.
- 9d ago First seen · 346 lines · 58 tokens per session scan A bfbe48887b4d
seo-content-audit is a skill published in the GitHub repository schwepps/skills (16 stars, last pushed 7mo ago), licensed MIT. It adds 58 tokens to every session and 2,205 once invoked, about $0.0003 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.
Other skills, from other repositories
stuck
Diagnoses a broken course setup by reading the folder, so the student never has to describe the problem in English. Takes no argument. Reports which class they are on and which files are filled, then names one blocker and one fix: Claude Code opened at the wrong level, .claude/skills/ missing, skills not loading…
grill-me
Two modes, picked from the file you point it at. Contract mode grills a claude-contract.md line by line until every line is a thing Claude must always do or must never do, editing that file in place and creating nothing new. Brief mode interrogates a design brief until it has no soft spots left, then produces a…
information-architecture
Map the user journey first, then derive the screen inventory, navigation and hierarchy from it, flagging any screen that serves no journey step. Writes the four-part markdown plus an HTML diagram of the step-to-screen mapping. Use after the brief is settled and before tokens or UI.
design-tokens
Establish color, typography, spacing, radius and motion as named role-based tokens. Use before building any interface.
heuristic-evaluation
Audit a design against Nielsen's ten usability heuristics, tying every finding to a specific element with a specific fix. Use on a built screen or a detailed mockup.
persona-acid-test
Stress-test a design through three lenses, confused user, skeptical engineer and impatient PM, before it goes to a stakeholder. Requires an actual design, an HTML file, Figma link or screenshot.