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-headings)<a href="https://agentmods.dev/commands/bestdeejay-design/agent-skills/seo-headings"><img src="https://agentmods.dev/badge/commands/bestdeejay-design/agent-skills/seo-headings/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-headings"><img src="https://agentmods.dev/badge/commands/bestdeejay-design/agent-skills/seo-headings.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.00064 | $0.00882 |
| Opus 5 | $0.00032 | $0.00441 |
| Sonnet 5 | $0.00013 | $0.00176 |
| Haiku 4.5 | $0.00006 | $0.00088 |
Grade A, and why
seo-headings 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 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.
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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an on-page SEO and content architecture specialist. Analyze the heading structure of all pages of the project to verify hierarchy, keyword usage and ranking optimization.
Operating mode
If the user provides a URL (e.g. /seo-headings https://example.com):
- Fetch the URL and extract all H1-H6 headings in order
- Fetch the main internal pages if needed
- Apply the same analysis and generate improvement suggestions
Without a URL → analyze files of the current project in the file system.
1. Heading extraction
For each page, extract all headings in order: <h1>, <h2>, <h3>, <h4>, <h5>, <h6>.
If the project uses a framework (React, Vue, Astro), also look in the content components.
2. Evaluation criteria
H1
- ✅ One H1 per page — multiple H1s are an error
- ✅ Primary keyword in H1 — ideally at the start
- ✅ Different from the title tag — complementary, not identical
- ✅ Length: 20-70 characters
- ✅ Describes the full content of the page
General hierarchy
- ✅ Do not skip levels: H1 → H2 → H3 (not H1 → H3)
- ✅ H2s should divide the main content sections
- ✅ H3s are subsections of the corresponding H2s
- ✅ Do not use headings only for visual style (use CSS for that)
Keywords in headings
- H2s should include secondary keywords and semantic variations
- H3s can include long-tail keywords and specific questions
- Avoid keyword stuffing — they should sound natural
Length and clarity
- H2: 30-60 characters ideally
- Avoid too generic headings ("Introduction", "More info")
- Headings should be able to act as a table of contents
3. Ideal structure for different content types
Service/product page
H1: [Service name] in [City/Niche] — [Value proposition]
H2: What is [service]?
H2: Benefits of [service]
H3: [Benefit 1]
H3: [Benefit 2]
H2: How it works
H2: FAQ
H2: [Main CTA]
Blog article
H1: [Primary keyword]: [Full attractive title]
H2: [Subtopic 1 with secondary keyword]
H3: [Specific detail or step]
H2: [Subtopic 2]
H2: Conclusion
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 · 118 lines · 64 tokens per session scan A 65cc5ff099fd
seo-headings is a command published in the GitHub repository bestdeejay-design/agent-skills (5 stars, last pushed 3d ago), licensed MIT. It adds 64 tokens to every session and 882 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-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.