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 agentmods add skills/gluestack/agent-skills/creating-componentsnpx skills add gluestack/agent-skills --skill creating-componentsgit 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/creating-components)<a href="https://agentmods.dev/skills/gluestack/agent-skills/creating-components"><img src="https://agentmods.dev/badge/skills/gluestack/agent-skills/creating-components.svg" alt="Measured on agentmods" 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 | $0.00040 | $0.05610 |
| Opus 5 | $0.00020 | $0.02805 |
| Sonnet 5 | $0.00008 | $0.01122 |
| Haiku 4.5 | $0.00004 | $0.00561 |
Grade A, and why
gluestack-ui-v4:creating-components 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 5d 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 — 878 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gluestack UI v4 - Creating Components
This sub-skill provides practical guidance for creating new components using gluestack-ui v4, from planning to implementation.
Component Creation Workflow
Step 1: Plan Component Structure
Before writing code, answer these questions:
-
What is the component's purpose?
- Form input, data display, navigation, layout, etc.
-
Which Gluestack components do I need?
- Check official docs:
https://v4.gluestack.io/ui/docs/components/${componentName}/ - Use Gluestack wrappers, not React Native primitives
- Check official docs:
-
Does it need compound components?
- Multiple related sub-components (Header, Body, Footer)
- Icon + Text combinations
- Label + Input patterns
-
What props should it accept?
- Size variants:
sm,md,lg - Visual variants:
default,outline,ghost - State props:
isDisabled,isInvalid,isLoading - Custom className for overrides
- Size variants:
-
Does it need variants?
- If yes, use
tva(Tailwind Variant Authority) - Define base styles and variant options
- If yes, use
Step 2: Check Official Documentation
ALWAYS verify component usage before creating:
# Visit official docs for the component
https://v4.gluestack.io/ui/docs/components/${componentName}/
Check for:
- Latest API and props
- Required sub-components
- Usage examples
- Accessibility features
Step 3: Create Component File
Follow this file structure:
components/
├── ui/ # Gluestack UI components (copy-paste)
│ ├── box/
│ ├── button/
│ └── input/
└── custom/ # Your custom components
├── profile-card/
│ └── index.tsx
└── login-form/
└── index.tsx
Component Templates
Template 1: Simple Component (No Variants)
Use when component has consistent styling without variants.
import React from 'react';
import { Box } from '@/components/ui/box';
import { Text } from '@/components/ui/text';
import { Heading } from '@/components/ui/heading';
interface ProfileCardProps {
readonly name: string;
readonly email: string;
readonly className?: string;
}
export const ProfileCard = ({ name, email, className }: ProfileCardProps) => {
return (
<Box className={`bg-card rounded-lg border border-border p-4 ${className || ''}`}>
<Heading size="lg" className="text-card-foreground">
{name}
</Heading>
<Text size="sm" className="text-muted-foreground mt-1">
{email}
</Text>
</Box>
);
};
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.
- 5d ago First seen · 878 lines · 40 tokens per session scan A aa752f5a7a95
gluestack-ui-v4:creating-components is a skill published in the GitHub repository gluestack/agent-skills (1 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 5,610 once invoked, about $0.0002 per session on Opus 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
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.