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/setupnpx skills add gluestack/agent-skills --skill setupgit 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/setup)<a href="https://agentmods.dev/skills/gluestack/agent-skills/setup"><img src="https://agentmods.dev/badge/skills/gluestack/agent-skills/setup.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.00051 | $0.01088 |
| Opus 5 | $0.00026 | $0.00544 |
| Sonnet 5 | $0.00010 | $0.00218 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade A, and why
gluestack-ui-v4:setup 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 3d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gluestack UI v4 - Setup & Installation
This sub-skill follows the official gluestack-ui v4 installation guide only. Nothing is followed from outside Installation | gluestack-ui v4.
Use either CLI or Manual as defined on that page.
v4 only – do not use v1/v2/v3 packages or docs
- Never use or suggest:
@gluestack/styled,@gluestack-ui/themed, or any packages/docs from gluestack.io (without thev4.subdomain). Those are for v1/v2/v3. - v4 uses: v4.gluestack.io docs only; packages such as
@gluestack-ui/core,@gluestack-ui/utils, NativeWind, and components copied into your app (e.g.GluestackUIProvider,icon,overlay,toast). Manual installation for v4 is only the Manual tab on the v4 Installation page – not any other “manual” or “gluestack styled” guide.
CLI
Step 1: Setup your project
Prerequisites
Ensure these prerequisites are satisfied to use the gluestack-ui CLI:
| Package Name | Supported Versions | Upcoming Support |
|---|---|---|
| next | 13 <= versions <= 15 | - |
| react-native | versions >= 72.5 | - |
| expo | versions >= 50 | - |
| node | versions > 16 | - |
Step 2: Initialize (CLI only)
To initialize gluestack-ui v4 via CLI, use only this command (from your project root):
npx gluestack-ui@alpha init -y
This adds GluestackUIProvider and essential components (icon, overlay, toast). Do not use any other command or method for CLI initialization.
After init, your project is ready to use gluestack-ui components. To add more components via CLI, use the add command or the CLI guide. Example:
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.
- 3d ago First seen · 87 lines · 51 tokens per session scan A 3be88451fed0
gluestack-ui-v4:setup is a skill published in the GitHub repository gluestack/agent-skills (1 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 1,088 once invoked, about $0.0003 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
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…
row-selection
Maintain rowSelection ID state with stable getRowId, single, multi, subrow, and Shift-range rules, selected row models, handler anchors, and manual-pagination semantics. Load when implementing getToggleSelectedHandler, enableRowRangeSelection, selectChildren, deselectParents, or selected IDs that outlive loaded Row…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
wrdn-effect-promise-exit
Replace React/effect-atom mutation handlers that use promise-mode plus try/catch with promiseExit and explicit Exit handling. Use when lint or review flags try/catch around useAtomSet mutation calls, especially UI handlers that set error/busy state after a failed mutation.
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
markstream-react
Integrate the beta markstream-react package into a React 18+ or Next app. Use when Codex needs to add the React renderer, choose the root, next, or server entrypoint, import CSS correctly, choose between content and nodes, keep client boundaries safe, add renderer-local streamingComponents or htmlComponents, use…