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/jonathanung/strike/tui-componentsnpx skills add jonathanung/strike --skill tui-componentsgit clone --depth 1 https://github.com/jonathanung/strikeWhat 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.00105 | $0.03524 |
| Opus 5 | $0.00053 | $0.01762 |
| Sonnet 5 | $0.00021 | $0.00705 |
| Haiku 4.5 | $0.00011 | $0.00352 |
Grade A, and why
tui-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 2d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TUI components (strike-cli)
internal/frontend/tui/theme is the resolved token source and internal/frontend/tui/ui is the
component library. Root views compose completed theme styles and ui
components, then perform only structural operations (joining, allocation,
selection, and layout). Keep this catalog synchronized with internal/frontend/tui/ui.
Boundaries
- Edit
internal/frontend/tui/app/_src/<group>/only for packagetui. Flattenedinternal/frontend/tui/app/*.goare gitignored and regenerated bygo generate ./internal/frontend/tui/app/ make / CI — edits there are silently lost. Real packagestheme,ui,term,commonare edited in place. internal/frontend/tui/...may import onlyinternal/protocol,internal/frontend/host,internal/frontend/tui/..., stdlib, and third-party packages. The boundary test enforces this. Kit packages (ui,theme,common,term) must not import protocol or host. Charm modules: v1github.com/charmbracelet/…or v2charm.land/…— nevergithub.com/charmbracelet/…/v2.internal/frontend/tui/uimay import only stdlib, lipgloss, bubbles,charmbracelet/x/ansi, andinternal/frontend/tui/theme; components do not import the app model or handletea.Msg. The Strike wordmark lives in the app.- Resolve a supplied theme before reading tokens:
th = th.Resolve(). Colors, glyphs, borders, spacing, and emphasis come only from that resolved theme. Never put literal colors, visual glyphs, border/spacing values, or visual modifiers in a root view. Auivisual-modifier argument must trace to a resolved theme value; manually review unknown or interprocedural origins. - Components are pure renderers: exported rendering functions take a
theme.Themeand options and return a string. State and key handling remain ininternal/frontend/tui/appmodel files.
Component catalog
Tone is ToneDefault, ToneAccent, ToneAccentAlt, ToneSuccess,
ToneWarning, ToneError, ToneDanger, or ToneMuted. Level is
LevelInfo, LevelSuccess, LevelWarning, or LevelError.
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.
- 2d ago First seen · 176 lines · 105 tokens per session scan A 10f9bcbd9912
tui-components is a skill published in the GitHub repository jonathanung/strike (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 105 tokens to every session and 3,524 once invoked, about $0.0005 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
design-guide
Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design…
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
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…
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.
author-component
Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable…
obsidian-layout-adjustment
Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, or CSS snippets.…