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 T4wroot/agentic-seo --skill popupgit 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/popup)<a href="https://agentmods.dev/skills/t4wroot/agentic-seo/popup"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/popup/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/t4wroot/agentic-seo/popup"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/popup.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.00078 | $0.00742 |
| Opus 5.5 | $0.00031 | $0.00297 |
| Sonnet 5.5 | $0.00016 | $0.00148 |
| Haiku 4.5 | $0.00008 | $0.00074 |
Grade A, and why
popup-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 1mo 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 popup-generator — 77 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Components: Popup / Modal
Guides popup and modal design for conversion. Well-designed popups can achieve up to 25% conversion; poorly timed or intrusive ones hurt UX and SEO. Google penalizes intrusive mobile popups.
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.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for offers and audience.
Identify:
- Goal: Newsletter, discount, lead magnet, demo
- Trigger: Time delay, scroll %, exit intent, click
- Mobile: Critical; smaller screens = easier to interrupt
Best Practices
Timing and Context
- Avoid: Popup on page load; users hate it
- Prefer: After engagement (scroll 25-50%, time on page, exit intent)
- Personalize: Returning visitors, cart abandoners, discount users
- Value-first: Offer genuine value; act as "helpful teammate" not spam
Design
- Short copy: Clear headline, one benefit, single CTA
- Visual hierarchy: Guide attention to CTA; don't distract
- Easy exit: Clear X, visible "No Thanks"; friction-free exit increases trust and conversion
- Brand consistency: Build instant comfort
Mobile
- Size: Fit screen; thumb-friendly close
- Lightweight: Avoid heavy assets; affects LCP
- SEO: Google penalizes intrusive interstitials; avoid full-page takeover on mobile
Avoid
- Dark patterns (fake close, hidden options)
- Too early or too frequent
- Multiple popups in one session
- Blocking content without clear value
Triggers
| Trigger | Use |
|---|---|
| Time delay | 5-15s typical; after some engagement |
| Scroll % | 25-50% read; user invested |
| Exit intent | Mouse leaving viewport; last chance |
| Click | User-initiated; least intrusive |
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.
- 1mo ago First seen · 77 lines · 78 tokens per session scan A b7e0be40f40d
popup-generator is a skill published in the GitHub repository T4wroot/agentic-seo (15 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 742 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to popup-generator, differing in 77 lines, and is treated as a copy.
Other skills, from other repositories
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…
brand-visual-generator
When the user wants to define, audit, or apply visual identity (typography, colors, spacing, design tokens, frontend aesthetics). Also use when the user mentions "brand style guide," "visual identity," "design system," "typography," "color palette," "brand guidelines," "AI brand aesthetics," "brand colors," "font…
image-optimization
When the user wants to optimize images for search engines and performance. Also use when the user mentions "image SEO," "alt text," "image captions," "figcaption," "image optimization," "WebP," "lazy loading," "LCP," "image sitemap," "responsive images," "srcset," "image format," or "hero image optimization." For CWV…