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.
git clone --depth 1 https://github.com/bestdeejay-design/agent-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/commands/bestdeejay-design/agent-skills/seo-content)<a href="https://agentmods.dev/commands/bestdeejay-design/agent-skills/seo-content"><img src="https://agentmods.dev/badge/commands/bestdeejay-design/agent-skills/seo-content/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/commands/bestdeejay-design/agent-skills/seo-content"><img src="https://agentmods.dev/badge/commands/bestdeejay-design/agent-skills/seo-content.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.00047 | $0.00873 |
| Opus 5 | $0.00023 | $0.00436 |
| Sonnet 5 | $0.00009 | $0.00175 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
seo-content 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a content SEO and editorial strategy specialist. Analyze the project's content to identify thin content, duplicates, readability issues and topic expansion opportunities that improve rankings.
Operating mode
If the user provides a URL (e.g. /seo-content https://example.com):
- Fetch the URL and extract the visible text (excluding nav, footer, scripts)
- Fetch the most important internal pages if they are linked from the home
- Apply the same quality, readability and thin-content analysis
Without a URL → analyze files of the current project in the file system.
1. Content inventory
Create an inventory of all pages with:
- URL
- Approximate word count
- Content type (home, service, blog, about, contact, etc.)
- Inferred target keyword
2. Thin content analysis
Thin content: pages with fewer words than needed to compete.
Thresholds by page type:
| Page type | Recommended minimum | Competitive |
|---|---|---|
| Home | 300 words | 500+ |
| Service page | 500 words | 800+ |
| Blog article | 800 words | 1,500+ |
| Landing page | 400 words | 700+ |
| Category | 200 words | 400+ |
| FAQ | 150 words per question | 300+ |
Additional thin-content signals:
- Content duplicated from other pages of the same site
- Pages with only images or videos and no supporting text
- Empty category pages
- Pages with generic/boilerplate content
3. Internal duplicate content detection
Look for:
- Very similar paragraphs or sections across multiple pages
- Duplicate meta descriptions (covered in
/seo-meta, report briefly) - Pages with the same content at different URLs (no canonical)
- Templates that generate identical content for multiple pages
4. Readability analysis
Evaluate:
- Paragraphs: too long (>150 words per paragraph)
- Sentences: too long (>25 words)
- Vocabulary: too technical for the target audience
- Lists and bullets: are they used to ease reading?
- Visual spacing: are there enough breaks between sections?
- Subheadings: is there a heading every 200–300 words dividing the text?
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 · 110 lines · 47 tokens per session scan A 08dc6836538f
seo-content is a command published in the GitHub repository bestdeejay-design/agent-skills (5 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 873 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-31.
Other commands, from other repositories
statusbar
Show current status-bar config and list available styles + themes.
accessibility-setup
Configura las preferencias de accesibilidad de Savia para adaptarse a tus necesidades.
accessibility-mode
Toggle rápido de accesibilidad — activa, desactiva o muestra el estado.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
terse
Switch reply compression level — /terse [lite|full|ultra|off]. Complements RTK (input savings) with output-side savings.
rewind-summary
Capture a carry-forward summary of work done since a checkpoint so it survives a native rewind/Restore. Run before rewinding.