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/listnpx skills add T4wroot/agentic-seo --skill listgit 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/list)<a href="https://agentmods.dev/skills/t4wroot/agentic-seo/list"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/list.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.00076 | $0.00765 |
| Opus 5 | $0.00038 | $0.00382 |
| Sonnet 5 | $0.00015 | $0.00153 |
| Haiku 4.5 | $0.00008 | $0.00076 |
Grade A, and why
list 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 3d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Components: List Layout
Guides list layout design for linear, stacked content display. Lists are compact, text-heavy; users scan by title or metadata. Used for blog indexes, documentation, search results, and dense content.
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.
When to Use List
| Use list when | Use grid when |
|---|---|
| Text-heavy; scan by title | Visual content; equal emphasis |
| Many items; compact display | Fewer items; browsing |
| Blog index, docs, search results | Products, templates, gallery |
| F-pattern reading (top-left, left column) | Discovery, exploration |
See grid for grid layout; card for card structure.
List Structure
| Element | Purpose |
|---|---|
| Items | Single column; stacked vertically |
| Per item | Title, optional metadata (date, author), excerpt, link |
| Spacing | Consistent gaps; dividers or alternating background |
| Density | Compact (docs) vs relaxed (blog) |
List Variants
| Variant | Use |
|---|---|
| Simple list | Title + link; minimal (nav, TOC) |
| Rich list | Title, excerpt, date, author |
| Table-like | Columns for metadata (date, status) |
| With thumbnail | Small image + text |
Best Practices
| Principle | Practice |
|---|---|
| Scannable | Clear titles; consistent hierarchy |
| Compact | Less vertical space than grid |
| Link area | Full row or title clickable |
| Metadata | Date, author, category; secondary styling |
F-Pattern
Users read top-left first, then scan left column. Place primary content (titles) left-aligned; metadata secondary.
Infinite Scroll
If using infinite scroll for list (e.g., blog index, search results): crawlers cannot access content loaded on scroll. Provide paginated component pages or use traditional pagination for SEO-critical content. See site-crawlability for search-friendly infinite scroll implementation.
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.
- 3d ago First seen · 76 lines · 76 tokens per session scan A 6c2bbb7d93d6
list is a skill published in the GitHub repository T4wroot/agentic-seo (14 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 765 once invoked, about $0.0004 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
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.
rank-schema
Structured data management. Detect, validate, generate, and inject JSON-LD schema.