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 PavloSEO/seohead-seotools --skill heading-outlinegit clone --depth 1 https://github.com/PavloSEO/seohead-seotoolsWrote 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/pavloseo/seohead-seotools/heading-outline)<a href="https://agentmods.dev/skills/pavloseo/seohead-seotools/heading-outline"><img src="https://agentmods.dev/badge/skills/pavloseo/seohead-seotools/heading-outline/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/pavloseo/seohead-seotools/heading-outline"><img src="https://agentmods.dev/badge/skills/pavloseo/seohead-seotools/heading-outline.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.00159 | $0.01155 |
| Opus 5 | $0.00079 | $0.00577 |
| Sonnet 5 | $0.00032 | $0.00231 |
| Haiku 4.5 | $0.00016 | $0.00115 |
Grade A, and why
heading-outline scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL -A 'Mozilla/5.0 (audit heading-outline)' "$URL" -o /tmp/page.html How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Heading Outline — H1–H6 Heading Structure and Hierarchy
Screaming Frog exports only H1/H2 and flags only "missing H1" / "multiple H1"
(see ../sf-analyzer/reference/checks.md: H1_MISSING, H1_MULTIPLE,
H2_MISSING). It does not provide a complete H1–H6 outline in document order
or check level jumps; the agent does this itself by parsing live HTML.
When to Use It
- "Check the headings / heading structure on the page";
- "Is the H1→H2→H3 hierarchy correct, with no level jumps?";
- "Build the page outline" or "inspect the Hx structure."
Workflow
- Get the URL list. Use the sf-analyzer audit (
audit.json→pages[].urlorInternal:All). If no URL was provided, ask for one page or a set of pages. Process each URL separately. - Download and parse the HTML in DOM order (requires
pip install lxml):
For a JS-heavy SPA,curl -sL -A 'Mozilla/5.0 (audit heading-outline)' "$URL" -o /tmp/page.html python - "$URL" <<'PY' import sys, re from lxml import html url = sys.argv[1] doc = html.parse('/tmp/page.html').getroot() # All h1..h6 elements in document order nodes = doc.xpath('//h1|//h2|//h3|//h4|//h5|//h6') out = [] for n in nodes: lvl = int(n.tag[1]) txt = re.sub(r'\s+', ' ', n.text_content()).strip() out.append((lvl, txt)) # Print the indented outline for lvl, txt in out: print(' ' * (lvl - 1) + f'H{lvl}: ' + (txt or '∅ (empty)')) PYcurlreturns an empty shell; in that case, use rendered HTML from sf-analyzer mode A (Store Rendered HTML), or warn that rendering is required. - Check the hierarchy using the collected
(level, text)list:- Exactly one H1. 0 →
H1_MISSING; ≥2 →H1_MULTIPLE(output every text). - No skipped levels. The level must not increase by more than 1 in a single step:
H3 may follow H2, but H2→H4 is an error (
HEADING_SKIP). A heading may drop to any level (H4→H2 is valid). - H1 comes first. If an H2+ occurs before the first H1 →
H1_NOT_FIRST. - H1 is not empty and does not match
<title>verbatim (H1_EQUALS_TITLE). - Text is meaningful: not empty, longer than ~2 characters, and not just numbers,
icons, "Read more," or "Read"; these are "decorative" headings
(
HEADING_DECORATIVE). - No duplicate text among headings on the same page (
HEADING_DUP_TEXT).
- Exactly one H1. 0 →
- Summarize the result. For each page, provide the indented outline (from step 2) plus a list of detected issues, including the level and text of the offending heading. For a set of pages, provide a summary such as "N pages with hierarchy issues" and the most common issue types.
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.
- 11d ago First seen · 79 lines · 159 tokens per session scan A 1f27b053b374
heading-outline is a skill published in the GitHub repository PavloSEO/seohead-seotools (0 stars, last pushed 8d ago), licensed MIT. It adds 159 tokens to every session and 1,155 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
fire-your-seo-agency
A procedure for improving how a website appears in search engines and how AI answer systems find and cite it. It covers search, answer-engine, generative-AI, and Naver visibility.
geo-loop
Run one bounded eGEOagents loop iteration over a workspace domain - read the charter and fresh collector data, do ONE unit of work, write substrate artifacts, append one Timeline entry and one LOG line. Use for loop mode, /geo:loop, scheduled GEO runs, or continuous monitoring.
content-scoring
Score content against the 10 GEO criteria with evidence and prioritized fixes. Use when users ask to score, rate, evaluate, or estimate ranking strength.
competitive-analysis
Analyze AI-search competitors for a query and recommend ranking strategy. Use when users ask competitor analysis, who ranks, or competitive landscape.
validation-doctor
Check Brave Search and Chrome DevTools MCP availability and provide exact setup snippets. Use when validation dependencies are missing or uncertain.
geo-content-research
Researches what prompts people ask AI engines (ChatGPT, Gemini, Perplexity, Claude) about a product category and produces a prompts.csv artifact — a prioritized, strictly-schema'd list of the queries where the brand should be cited. Feeds the monitor workflow.