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 cardgit 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/card)<a href="https://agentmods.dev/skills/t4wroot/agentic-seo/card"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/card/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/card"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/card.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.00072 | $0.01112 |
| Opus 5.5 | $0.00029 | $0.00445 |
| Sonnet 5.5 | $0.00014 | $0.00222 |
| Haiku 4.5 | $0.00007 | $0.00111 |
Grade A, and why
card 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 card — 87 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Components: Card Layout
Guides card layout design for scannable, responsive content display. Cards are self-contained containers that group related content; used in grids for blog posts, products, templates, tools, features, galleries, and integrations.
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.
Card Anatomy
| Element | Purpose |
|---|---|
| Container | Border, background, shadow; consistent padding |
| Image / Thumbnail | Visual anchor; consistent aspect ratio (1:1, 4:3 common) |
| Title | Clear; keyword-rich where relevant |
| Description / Metadata | Supporting text; date, author, category |
| CTA | Action button or link; "View," "Use," "Connect," etc. |
Principle: One card = one topic. Keep each card focused for scannability.
Card Types by Use Case
| Type | Typical Elements | Page Skill |
|---|---|---|
| Product card | Image, name, price, CTA (Add to cart, View) | products-page-generator |
| Template card | Thumbnail, name, short description, "Use" or "Preview" CTA | template-page-generator |
| Tool card | Name, one-line benefit, CTA to tool page | tools-page-generator |
| Feature card | Name, benefit, optional screenshot | features-page-generator |
| Gallery / Showcase item | Thumbnail, title, creator, link | showcase-page-generator |
| Integration card | Logo, name, short description, "Connect" or "Install" | integrations-page-generator |
| Blog / Article card | Cover image, title, excerpt, date, author | blog-page-generator, article-page-generator |
| Resource card | Thumbnail, title, format (guide, webinar), CTA | resources-page-generator |
Layout & Responsiveness
- Grid: CSS Grid
repeat(auto-fill, minmax())or Flexbox; columns adapt to viewport - Mobile: Single column on small screens; 2–4 columns on desktop
- Consistency: Same padding, spacing, and aspect ratios across cards
- Hover: Subtle elevation (shadow, translate-y); avoid scale that causes layout shift (CLS)
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 · 87 lines · 72 tokens per session scan A ce98d67c1488
card is a skill published in the GitHub repository T4wroot/agentic-seo (15 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 1,112 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 card, differing in 87 lines, and is treated as a copy.
Other skills, from other repositories
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…
tab-accordion
When the user wants to add or optimize tab or accordion components for content organization. Also use when the user mentions "tab component," "accordion," "expandable content," "collapsible sections," "tabbed content," "FAQ accordion," "how-to tabs," "horizontal tabs," "vertical accordion," "content in tabs," "hidden…
favicon-generator
When the user wants to implement, optimize, or audit favicon and app icons. Also use when the user mentions "favicon," "app icon," "browser icon," "touch icon," "PWA icon," "favicon sizes," "apple-touch-icon," "favicon.ico," "site icon," or "tab icon." For visual system, use brand-visual-generator.
comparison-table-generator
When the user wants to create, optimize, or audit a comparison table section—an in-page block (HTML table or responsive equivalent) comparing products, methods, or approaches, with optional supporting copy. Also use when the user mentions "comparison table," "compare table," "feature matrix," "vs table," "side-by-side…
hero-generator
When the user wants to design, optimize, or audit hero sections (above-the-fold main visual area). Also use when the user mentions "hero," "hero section," "hero area," "above the fold," "above the fold content," "landing hero," "main banner," "banner section," "first fold," "hero section design," "hero conversion,"…
logo-generator
When the user wants to optimize logo placement, linking, or branding on a website. Also use when the user mentions "logo," "brand logo," "header logo," "logo placement," "AI logo design," "logo link," "logo alt text," "logo sizing," "favicon logo," or "logo usage." For full brand visuals, use brand-visual-generator.