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 gluestack/agent-skills --skill variantsgit clone --depth 1 https://github.com/gluestack/agent-skillsWrote 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/gluestack/agent-skills/variants)<a href="https://agentmods.dev/skills/gluestack/agent-skills/variants"><img src="https://agentmods.dev/badge/skills/gluestack/agent-skills/variants/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/gluestack/agent-skills/variants"><img src="https://agentmods.dev/badge/skills/gluestack/agent-skills/variants.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.00038 | $0.06186 |
| Opus 5.5 | $0.00015 | $0.02474 |
| Sonnet 5.5 | $0.00008 | $0.01237 |
| Haiku 4.5 | $0.00004 | $0.00619 |
Grade A, and why
gluestack-ui-v4:variants 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.
How it starts
The opening of the file, as written. The whole thing — 887 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gluestack UI v4 - Creating Component Variants
This sub-skill focuses on creating custom variants for existing gluestack-ui v4 components, allowing you to extend the design system with project-specific styling patterns while maintaining consistency and type safety.
When to Create a Variant
Create a new variant when:
- Repeating the same style combination - Multiple places use the same className pattern
- Project-specific design patterns - Brand-specific button styles, card types, etc.
- Conditional styling - Component appearance changes based on props
- Extending existing components - Adding new visual styles to Gluestack components
- Theme-specific variations - Different appearances for specific contexts
Don't create variants for:
- One-off custom styles (use className instead)
- Simple modifications (use existing props + className)
- Styles that should be in the global design system
Variant Creation Workflow
Step 1: Analyze the Component
Before creating a variant, understand:
- What's the base component? - Button, Card, Badge, etc.
- What visual states are needed? - Colors, sizes, borders, shadows
- Are there sub-components? - ButtonText, CardHeader, etc.
- What props should control variants? - variant, size, state props
- Should variants affect children? - Parent variants for sub-components
Step 2: Plan Variant Structure
Define your variant system:
// Example: Planning a Badge component with variants
{
variant: ['default', 'success', 'warning', 'error', 'info']
size: ['sm', 'md', 'lg']
shape: ['rounded', 'pill', 'square']
}
Step 3: Implement with tva
Use tva (Tailwind Variant Authority) to create type-safe, composable variants.
Creating Simple Variants
Template: Adding Variants to a Custom Component
import React from 'react';
import { tva } from '@gluestack-ui/utils/nativewind-utils';
import { Box } from '@/components/ui/box';
import { Text } from '@/components/ui/text';
interface BadgeProps {
readonly variant?: 'default' | 'success' | 'warning' | 'error' | 'info';
readonly size?: 'sm' | 'md' | 'lg';
readonly shape?: 'rounded' | 'pill' | 'square';
readonly className?: string;
readonly children: React.ReactNode;
}
// Define variant styles
const badgeStyles = tva({
base: 'inline-flex items-center justify-center font-medium',
variants: {
variant: {
default: 'bg-muted text-muted-foreground',
success: 'bg-primary/10 text-primary border border-primary/20',
warning: 'bg-accent/10 text-accent-foreground border border-accent/20',
error: 'bg-destructive/10 text-destructive border border-destructive/20',
info: 'bg-secondary/10 text-secondary-foreground border border-secondary/20',
},
size: {
sm: 'px-2 py-0.5 text-xs',
md: 'px-3 py-1 text-sm',
lg: 'px-4 py-1.5 text-base',
},
shape: {
rounded: 'rounded-md',
pill: 'rounded-full',
square: 'rounded-none',
},
},
defaultVariants: {
variant: 'default',
size: 'md',
shape: 'rounded',
},
});
export const Badge = ({
variant,
size,
shape,
className,
children
}: BadgeProps) => {
return (
<Box className={badgeStyles({ variant, size, shape, class: className })}>
<Text>{children}</Text>
</Box>
);
};
// Usage:
// <Badge variant="success" size="lg" shape="pill">Active</Badge>
// <Badge variant="error" size="sm">Error</Badge>
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 · 887 lines · 38 tokens per session scan A 59037448bc3c
gluestack-ui-v4:variants is a skill published in the GitHub repository gluestack/agent-skills (1 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 6,186 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
anti-slop-design
Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.
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 $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
open-design-setup
Prepare or repair a project's prototyping environment so open-design can build prototypes with the project's own component library and render them through the project's toolchain. Use when the library target is needed and docs/design/prototyping.md is missing, stale, or failing; excludes HTML-only design work and…
frontend-visual-qa
Audits rendered UI and specific task/object-link handoffs; excludes ordinary source citations alone. Audits already-rendered UI and Markdown/Obsidian image layout — web app, deck/slide, dashboard, design-system, or Electron/native app — via real-browser/native-app journeys and a Playwright sweep. Use after UI…