Borrowing it
Nothing to install: this file belongs to theexperiencecompany/gaia-ui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/theexperiencecompany/gaia-ui/main/.agents/skills/port-component/SKILL.mdgit clone --depth 1 https://github.com/theexperiencecompany/gaia-uiWrote 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/theexperiencecompany/gaia-ui/port-component)<a href="https://agentmods.dev/skills/theexperiencecompany/gaia-ui/port-component"><img src="https://agentmods.dev/badge/skills/theexperiencecompany/gaia-ui/port-component/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/theexperiencecompany/gaia-ui/port-component"><img src="https://agentmods.dev/badge/skills/theexperiencecompany/gaia-ui/port-component.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00113 | $0.02781 |
| Opus 5 | $0.00056 | $0.01391 |
| Sonnet 5 | $0.00023 | $0.00556 |
| Haiku 4.5 | $0.00011 | $0.00278 |
Grade A, and why
port-component 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 7d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Port Component from Gaia Mono Repo
Copies a component from the gaia mono repo into this repo (gaia-ui), makes it a reusable open-source component, and wires up registry, preview, and docs.
- Source repo:
~/work/gaia(override withGAIA_REPOenv var). Remote:https://github.com/theexperiencecompany/gaia - Default ref:
origin/master. Use another branch or ref only if the user asks. - Destination:
registry/new-york/ui/in this repo.
Never check out branches in the gaia repo. Read files with git show <ref>:<path> so the user's working tree there stays untouched.
Accepting the request
The user identifies the component in one of three ways:
- Component name ("port the footer"). Run the finder script (step 1 below).
- File path ("apps/web/src/components/navigation/Footer.tsx"). Read it directly with
git show. - Screenshot of UI from heygaia.io. Look at the image, identify what the component is (footer, navbar, pricing section, chat bubble, etc.), then search for it by that name and by distinctive strings visible in the screenshot (
git grep -i "Request a Feature" origin/master -- apps/web).
If it is still ambiguous after searching, show the user the candidate paths and ask.
Where to look in the gaia repo
Only search frontend code. Never search backend, infra, or tooling.
Search these paths, in this order:
| Path | What lives there |
|---|---|
apps/web/src/components/ |
Shared web components (ui/, navigation/, layout/, shared/, seo/) |
apps/web/src/features/<feature>/components/ |
Feature components (chat, landing, pricing, mail, calendar, settings, onboarding, ...) |
apps/web/src/config/ |
App config the components import (appConfig.tsx has footerSections, connect, nav links) |
apps/web/src/lib/, apps/web/src/hooks/ |
Helpers and hooks components may depend on |
apps/web/src/stores/ |
Zustand stores (strip these when porting, replace with props) |
Do NOT look in: apps/api (Python backend), apps/bots, apps/bridge, apps/voice-agent, infra, tools, scripts, packages/cli, docs, openspec. apps/mobile and apps/desktop only if the user explicitly asks for a mobile or desktop component.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 167 lines · 113 tokens per session scan A e3f2d9d62a05
port-component is a skill published in the GitHub repository theexperiencecompany/gaia-ui (219 stars, last pushed 9d ago), licensed MIT. It adds 113 tokens to every session and 2,781 once invoked, about $0.0006 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-09-05.
Other skills, from other repositories
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
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…
port-sacred-terminal-ui-to-hostile-react-codebase
Take a sacred React component (or a sacred screen that mirrors a Simulacrum CLI surface) and graft it into a foreign React codebase that already ships its own design system, build pipeline, and CSS toolchain — without breaking the host or polluting it with sacred-specific globals.
port-sacred-terminal-ui-to-react-using-same-conventions
Take a CLI screen written for Simulacrum — the sacred CLI framework (scripts/cli/templates/.ts or scripts/python/templates/.py) — and produce a React component that lives inside components/examples/ (or components/) using only sacred's existing primitives — Window, Card, SimpleTable, ActionButton, RowSpaceBetween…
heroui-native
HeroUI Native component library for React Native (Tailwind v4 via Uniwind). Use when building mobile UIs with HeroUI Native — creating Buttons, Cards, TextFields, Dialogs; installing heroui-native; configuring dark/light themes; or fetching component docs. Keywords: HeroUI Native, heroui-native, React Native UI…