thurbox-ui

Instructions for editing the live thurbox text-based interface, whose panes are defined by Lua files. They explain how to find the active interface directory and how to add, change, or remove panes, layouts, and keybindings.

In plain words
What is it for?
Use them when changing what thurbox shows or how it behaves on screen, including panels, pane arrangements, keyboard shortcuts, and status displays.
Why use it?
They prevent edits to the wrong copy of the interface, such as a checkout that is not loaded by thurbox. They also make clear that interface changes belong in Lua configuration files rather than Rust source code.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/thurbeen/thurbox/ui-skill
Any agent
npx skills add Thurbeen/thurbox --skill ui-skill
Clone the repo
git clone --depth 1 https://github.com/Thurbeen/thurbox

Made for: Claude Code, Codex.

Per session 122 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,485 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00122 $0.03485
Opus 5 $0.00061 $0.01742
Sonnet 5 $0.00024 $0.00697
Haiku 4.5 $0.00012 $0.00348

Measured 2d ago against content hash e782557cf7de, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

thurbox-ui 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.

extensions/ui-skill/SKILL.md · 258 lines

How it starts

The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Editing the thurbox interface

Managed by thurbox extension install — see Updating this skill at the bottom before editing it.

thurbox's interface has no built-in screen underneath. Every pane is a Lua file in one directory, the kernel reads that directory at startup, and saving a file reloads it. Changing the TUI means editing Lua there — never Rust, and never the repository this session happens to be sitting in.

First: find the directory

The interface is not in the current repo. It is a config directory of the user's, so it is almost always outside this session's worktree:

thurbox-cli plugin dir     # the directory in force, and which rule chose it

Two rules pick it: THURBOX_UI_DIR if set, otherwise the user's own copy — ~/.config/thurbox/ui, or ~/.config/thurbox-dev/ui for a dev build. Run the command; do not assume which. If you cannot write outside this session's worktree, say so and ask for that path to be allowed — do not edit something else instead and report it as done.

A thurbox checkout's ui/ is not the live interface. Editing ui/ inside a clone of the thurbox repository changes nothing on screen unless THURBOX_UI_DIR points at it (just tui-ui in that repo does exactly that). If the user wants their running thurbox changed, the destination is plugin dir's answer. If they want the shipped interface changed, it is the checkout, and that is a code change with a pull request behind it — ask which they mean when both are plausible.

Then: read the directory's own docs

The directory ships the reference, and it is versioned with the binary the user is running, so it is more current than anything you remember:

UI="$(thurbox-cli plugin dir --text | head -1)"   # or: plugin dir --json | jq -r .dir
cat "$UI/AGENTS.md"    # the operational half — what is easy to get wrong
cat "$UI/README.md"    # the reference — node kinds, the API, the traps
cat "$UI/layout.lua"   # the arrangement — which slots exist and where
ls "$UI/plugins" "$UI/lib"

Read the full file on GitHub · 258 lines

Files

What ships with it

2 files 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.

Changes

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.

  1. 2d ago First seen · 258 lines · 122 tokens per session scan A e782557cf7de

Subscribe to this mod's changes

thurbox-ui is a skill published in the GitHub repository Thurbeen/thurbox (57 stars, last pushed 3d ago), licensed MIT. It adds 122 tokens to every session and 3,485 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-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens