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 ariadoss/superskills --skill cardgit clone --depth 1 https://github.com/ariadoss/superskillsWrote 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/ariadoss/superskills/card)<a href="https://agentmods.dev/skills/ariadoss/superskills/card"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/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/ariadoss/superskills/card"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/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 | $0.00036 | $0.00556 |
| Sonnet 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 6d 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 — 0 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.
- 6d ago First seen · 87 lines · 72 tokens per session scan A ce98d67c1488
card is a skill published in the GitHub repository ariadoss/superskills (9 stars, last pushed 5d ago), licensed MIT. It adds 72 tokens to every session and 1,112 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to card, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…