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 agentmods add skills/t4wroot/agentic-seo/howto-sectionnpx skills add T4wroot/agentic-seo --skill howto-sectiongit clone --depth 1 https://github.com/T4wroot/agentic-seoWrote 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/t4wroot/agentic-seo/howto-section)<a href="https://agentmods.dev/skills/t4wroot/agentic-seo/howto-section"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/howto-section.svg" alt="Measured on agentmods" 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 | $0.00194 | $0.03072 |
| Opus 5 | $0.00097 | $0.01536 |
| Sonnet 5 | $0.00039 | $0.00614 |
| Haiku 4.5 | $0.00019 | $0.00307 |
Grade A, and why
howto-section-generator 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 5d 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.
This is a copy
100% identical to howto-section-generator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Components: HowTo Section
Guides HowTo as an in-page section: a block of ordered steps (and optional HowTo JSON-LD) embedded inside article, documentation, tool, or landing pages. Not a standalone page type—parent page structure and templates come from article-page-generator, docs-page-generator, tools-page-generator, landing-page-generator, etc. Distinct from FAQ (Q&A → FAQPage) and from full article body drafting alone (article-content). schema-markup remains the source for exhaustive Schema.org property rules and type-wide tables; this skill owns section-level placement, copy, HTML, and HowTo-vs-FAQ decisions.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
HowTo Section vs FAQ Section
| Dimension | HowTo section | FAQ section |
|---|---|---|
| Intent | User follows ordered steps to complete a task | User reads Q&A pairs for doubts |
| Structure | Steps (1→2→3), optional tools/time/supplies | Question → answer per item |
| Schema | HowTo (Schema.org) | FAQPage |
| UI | Often horizontal tabs for steps; or numbered list in flow | Often vertical accordion |
| Skill | howto-section-generator (this) | faq-page-generator |
Do not mark FAQ content as HowTo or vice versa; schema must match visible content.
Placement Within the Parent Page
This section is always part of a larger page. Typical positions:
| Location | When |
|---|---|
| After intro (and optional TL;DR / Key Takeaways) | Article: context first, then solution = steps |
| As the main middle of the page | Tutorial-heavy article where the HowTo block carries most of the value |
| After product/tool context | Tool or LP: short context → How to use steps → FAQ/CTA |
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.
- 5d ago First seen · 173 lines · 194 tokens per session scan A 841e721df7c6
howto-section-generator is a skill published in the GitHub repository T4wroot/agentic-seo (14 stars, last pushed 2d ago), licensed MIT. It adds 194 tokens to every session and 3,072 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to howto-section-generator, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
geo
完整的 GEO（生成式引擎优化）服务流水线：给一个产品官网 URL 和介绍材料， 做站点诊断与 AI 答案采样、生成带验收标准的执行工单、产出可直接部署的资产 （llms.txt / JSON-LD / 定义块 / FAQ / 内容大纲与初稿）、自动验收工单是否闭环、 并打包成可直接发给客户的交付物。可按周期复跑，做长期 GEO 运营与月报。 国内和海外双市场并行：国内覆盖 智谱GLM/豆包/DeepSeek/Kimi/MiniMax/纳米AI/百度AI， 海外覆盖 Gemini/ChatGPT/Claude/Grok/Perplexity，问题库与指标按市场分开算。 当用户说「做 GEO」「生成式引擎优化」「让 AI…
fire-your-seo-agency
SEO·AEO·GEO·LLMO·NEO(네이버) 다섯 레인을 진단하고 직접 구현하는 스킬. 사이트를 검색엔진·답변엔진·생성 AI·네이버 AI 브리핑이 인용하는 1차 소스로 만든다. "SEO 해줘", "AI에 인용되게 해줘", "네이버 노출 늘려줘", "llms.txt 만들어줘" 류 요청에 사용. Use for "audit my site's SEO", "get my site cited by ChatGPT/Perplexity/AI Overviews", "improve search visibility", "create llms.txt", "answer engine /…
rank-audit
Full SEO/GEO/AEO/Citability/Content/Performance/Vertical/Security audit with auto-fix. Scans, reports, fixes, and verifies.
rank-aeo
Answer engine optimization. Optimize for featured snippets, voice search, People Also Ask.
rank-geo
AI search optimization audit. Optimize content for ChatGPT, Perplexity, Google AI Overviews.
rank-fix
Auto-fix all SEO/GEO/AEO findings in one command. Scan, fix, verify.