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 dalroot/agentic-seo --skill rendering-strategiesgit clone --depth 1 https://github.com/dalroot/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/dalroot/agentic-seo/rendering-strategies)<a href="https://agentmods.dev/skills/dalroot/agentic-seo/rendering-strategies"><img src="https://agentmods.dev/badge/skills/dalroot/agentic-seo/rendering-strategies/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/dalroot/agentic-seo/rendering-strategies"><img src="https://agentmods.dev/badge/skills/dalroot/agentic-seo/rendering-strategies.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.00092 | $0.01528 |
| Opus 5.5 | $0.00037 | $0.00611 |
| Sonnet 5.5 | $0.00018 | $0.00306 |
| Haiku 4.5 | $0.00009 | $0.00153 |
Grade A, and why
rendering-strategies 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 today.
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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Technical: Rendering Strategies
Guides rendering strategy selection and optimization for search engine and AI crawler visibility. Golden rule: Page data and metadata must be available on page load without JavaScript execution for optimal SEO.
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.
Scope (Technical SEO)
- Static vs dynamic: SSG, SSR, ISR, CSR; when to use each
- Crawler behavior: Googlebot renders JS (with delays); AI crawlers do not
- Component-level: Content in initial HTML; tabs, carousels, nav
- Dynamic rendering: Prerender for bots when full SSR/SSG is not feasible
Rendering Methods
| Method | When HTML generated | SEO | Best for |
|---|---|---|---|
| SSG (Static Site Generation) | Build time | ✅ Best | Blog, docs, marketing pages; content rarely changes |
| SSR (Server-Side Rendering) | Request time | ✅ Good | News, product pages; dynamic, personalized content |
| ISR (Incremental Static Regeneration) | Build + revalidate | ✅ Good | Large sites; static with periodic updates |
| CSR (Client-Side Rendering) | Browser (after JS) | ❌ Poor | Dashboards, account pages; no SEO needed |
| Dynamic rendering | On-demand for bots | ✅ Fallback | SPAs; prerender for crawlers, SPA for users |
SSG (Static Site Generation)
HTML generated at build time; same HTML for every request. Best for SEO: crawlers receive full HTML immediately; optimal performance.
- Use when: Blog, docs, marketing pages, content that doesn't change frequently
- Framework: Next.js
getStaticProps, Astro, Gatsby
SSR (Server-Side Rendering)
HTML generated on each request. Good for SEO: crawlers receive complete HTML; supports dynamic, personalized content.
- Use when: News, product pages, user-specific content
- Tradeoff: Higher server load; slower TTFB than SSG
- Framework: Next.js
getServerSideProps, Remix
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.
- today First seen · 117 lines · 92 tokens per session scan A 8330f2551374
rendering-strategies is a skill published in the GitHub repository dalroot/agentic-seo (25 stars, last pushed 6d ago), licensed MIT. It adds 92 tokens to every session and 1,528 once invoked, about $0.0004 per session on Opus 5.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-10-26.
Other skills, from other repositories
docs-page-generator
When the user wants to create, optimize, or structure a documentation site. Also use when the user mentions "docs," "documentation site," "docs subdomain," "docs.yourdomain.com," "help center," "knowledge base," "Getting Started," "API Reference," "user guides," or "tutorials." For API marketing landing, use…
api-page-generator
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use…
seo
Deterministic LLM-first SEO audits for websites, blog posts, and GitHub repositories. Use this when the user asks to "perform SEO analysis", "run SEO audit", "analyze SEO", "check technical SEO", "review schema", "Core Web Vitals", "E-E-A-T", "hreflang", "GEO", "AEO", or GitHub repository SEO optimization. For…
github
When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists. Also use when the user mentions "GitHub," "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome list," "GitHub README," "profile README," "pinned repositories," "Trending,"…
schema-markup
When the user wants to add or optimize structured data (Schema.org, JSON-LD). Also use when the user mentions "schema," "structured data," "JSON-LD," "rich results," "rich snippets," "Google rich snippets," "featured snippet schema," "add schema to page," "missing structured data," "schema validation error," "Schema…
grokipedia-recommendations
When the user wants to add recommendations, links, or content to Grokipedia. Also use when the user mentions "Grokipedia," "GEO wiki," "AI encyclopedia," "suggest Grokipedia article," "Grokipedia citation," "Grokipedia listing," "AI search citation," "GEO visibility," or "Grokipedia optimization." For multi-platform…