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 herogit 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/hero)<a href="https://agentmods.dev/skills/t4wroot/agentic-seo/hero"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/hero/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/hero"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/hero.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.00099 | $0.01393 |
| Opus 5.5 | $0.00040 | $0.00557 |
| Sonnet 5.5 | $0.00020 | $0.00279 |
| Haiku 4.5 | $0.00010 | $0.00139 |
Grade A, and why
hero-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 hero-generator — 130 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Components: Hero Section
Guides hero section design for conversion and first impressions. The hero is where users spend ~80% of initial viewing time; first impressions form in milliseconds.
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 value proposition, audience, and Section 12 (Visual Identity).
Identify:
- Page type: Homepage, landing, product, pricing
- Primary goal: Signup, trial, purchase, learn more
- Platform: Web, mobile, both
Core Components (Four Essentials)
- Headline (H1): 6–10 words max; instantly communicate core value and benefit. Answer "What's in it for me?" within seconds.
- Subheading: Clear, concise explanation reinforcing why the product/service is valuable.
- Primary CTA: Single, prominent action button visible without scrolling. One per hero to avoid choice overload.
- Visual: High-quality image, video, or animation that amplifies the message.
Optional but Effective
- Trust cues: 1–3 elements (reviews, logos, statistics)
- Secondary CTA: For users not ready for primary action
Layout Types
Hero is a Spotlight layout—single focus, primary element with secondary around it. Choose layout by content balance and conversion goal.
| Layout | Structure | Best for |
|---|---|---|
| Split (50/50) | Text left, visual right (or vice versa); equal weight | Product, SaaS; clear value + demo |
| Split (75/25) | Text dominant; smaller image column | Copy-heavy; trust-first |
| Split (25/75 "Signpost") | Small image beside primary content | Minimal visual; emphasis on headline |
| Centered | Text + CTA centered; visual full-width or stacked | Brand, landing; single CTA |
| Full-width image | Image background; overlay text | Emotional; lifestyle, brand |
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 · 130 lines · 99 tokens per session scan A ea693c0b0fac
hero-generator is a skill published in the GitHub repository T4wroot/agentic-seo (15 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 1,393 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to hero-generator, differing in 130 lines, and is treated as a copy.
Other skills, from other repositories
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
scrollcraft
Premium scroll-driven landing pages; scroll = timeline.
web-design
Penguin visual language for generated web pages and app UIs — GitHub-style simplicity with a single blue accent, light and pure-black dark themes, design tokens, component and chat-interface recipes, plus an opt-in warm paper editorial theme.
building-landing-home
Compose a product or documentation home page from the @lobehub/ui/awesome landing components: LandingHero, AgentSkillCard, LogoMarquee, LandingSection, BentoGrid/BentoCard, CodeShowcase, FeatureGrid, InstallBanner and FluidGradient. Covers page structure, the lobedocs homePage hook, router links, theming the accent…
ui-craft
Design, build, redesign, or modify browser-visible web interfaces with product-quality composition, visual systems, interaction states, responsive behavior, accessibility, and browser visual QA. Use for HTML, CSS, JavaScript, React, Vue, or Svelte pages and components, landing pages, dashboards, admin tools, settings…
design-context-extract
Extract design DNA from app screenshots, live URLs, or screen recordings using Google Stitch — color palettes, typography, spacing tokens, component patterns, and motion specs as design-tokens.json or Tailwind config. Use when the user points to a screenshot, URL, or video and asks to extract or audit the design…