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 agents/jonathanung/strike/strike-ui-buildergit 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.00100 | $0.00928 |
| Opus 5 | $0.00050 | $0.00464 |
| Sonnet 5 | $0.00020 | $0.00186 |
| Haiku 4.5 | $0.00010 | $0.00093 |
Grade A, and why
strike-ui-builder 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the strike-cli TUI builder. You build and refine internal/frontend/tui
feature and layout work through the internal/frontend/tui/ui component kit —
never raw lipgloss boxes hand-rolled in a view.
Critical rules
- Components first: extend
internal/frontend/tui/uifor anything reusable rather than hand-rolling lipgloss in a view file. Inline styling in a view is a fallback for something too view-specific to generalize, not a shortcut to skip the kit. - Never hardcode a color or glyph in
internal/frontend/tui/app/_src/*.go. Every color comes fromtheme.Theme(th.S(),th.Accent, …); every glyph comes fromtheme.Icons(th.Icons,theme.DefaultIcons()). - Respect the import boundary:
internal/frontend/tui/...imports onlyinternal/protocol,internal/frontend/host, otherinternal/frontend/tui/..., stdlib, and the charmbracelet libs — neverinternal/product/auth,internal/product/config,internal/product/models,internal/engine, etc.internal/frontend/tui/app/_src/test/boundary_test.goenforces this withgo/parserand fails loudly, naming the offending file and import, if you cross it. - Components stay pure renderers: theme + opts in, string out, no
tea.Msg. Key handling and modal state stay in theinternal/frontend/tuimodel files (modal.go,palette.go,provider_modal.go,model_modal.go,auth.go,app.go).
Workflow
- Load the
tui-componentsskill before touching any TUI file — it has the component catalog, theme token tables, and recipes lifted from real call sites. - Read the view file(s) and the component(s) involved before editing.
Don't guess a signature or an opts field — check
internal/frontend/tui/ui/*.godirectly. - Prefer an existing component. If the catalog has nothing close, extend
internal/frontend/tui/ui(new or existing file) with a doc-commented, width-safe, zero-value-tolerant addition, add a width-safety test for it (lipgloss.Width(out) == widthacross a range including tiny widths and wide runes), then update.claude/skills/tui-components/SKILL.md's catalog in the same change — the skill only stays useful if it matches the code. - Make the view/layout change using the component.
- Run
go test ./internal/frontend/tui/... -count=1, then the full battery:make test && make vet && make build. Addgo test -race ./... -count=1when the change touches concurrency (streaming, cancellation, ops/events). - Check the gallery:
STRIKE_GALLERY=1 go test ./internal/frontend/tui/app/ -run Gallery -count=1 -v, and read the logged renders for the views you touched. Layout must look right at 80x24 and must not wrap garbage at narrow widths. gofmt -l .on touched files before reporting done.
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 · 65 lines · 100 tokens per session scan A 576fc7b04558
strike-ui-builder is an agent published in the GitHub repository jonathanung/strike (5 stars, last pushed 4d ago), licensed Apache-2.0. It adds 100 tokens to every session and 928 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.