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/thurbeen/thurbox/thurbox-performancenpx skills add Thurbeen/thurbox --skill thurbox-performancegit clone --depth 1 https://github.com/Thurbeen/thurboxWhat 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.00106 | $0.02730 |
| Opus 5 | $0.00053 | $0.01365 |
| Sonnet 5 | $0.00021 | $0.00546 |
| Haiku 4.5 | $0.00011 | $0.00273 |
Grade A, and why
thurbox-performance 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thurbox render-loop performance
Working reference extracted from CLAUDE.md, which indexes it. The rationale behind these decisions is owned by the docs under docs/; a change that invalidates what this says updates it in the same PR.
Performance (render loop)
The loop is demand-driven: it paints when something changed or when the 250 ms
forced-redraw floor (FORCE_REDRAW_INTERVAL) elapses, never on every iteration.
There are two floors between paints, because typing has to feel instant and
watching a log scroll does not: MIN_FRAME_INTERVAL (16 ms) when a person did
something — a key, a resize, a worker result they asked for, tracked by
input_dirty, which is set with dirty through the one App::note_input and
never alone — and OUTPUT_FRAME_INTERVAL (33 ms) when the only thing owing a
frame is agent output. Applying the tight floor to both made a chatty agent drive
60 paints a second to show 30 lines; the split is worth 30% of the loaded cost
(ADR-P17). What marks the screen dirty:
any input, a resize, a reload, a worker result, and new agent output —
Terminals::output_generation is summed each iteration, which is what stops a
printing agent being drawn at 4 fps. A reflow — the arrangement placing a
slot at a new rect, so a column opened or closed — additionally forces one full
repaint: the cell diff is only correct while ratatui and the terminal agree on a
glyph's width, and where they cannot (a flag, an emoji presentation sequence) the
pane that closed leaves characters behind.
kernel::paint::normalize_ambiguous_width strips the one such disagreement that
is strippable — U+FE0F — from every painted cell, panes and vt100 surfaces
alike, and kernel::paint::force_full_repaint covers the rest by marking every
cell of the reflowed frame as one the diff must print. It is deliberately not
Terminal::clear: erasing flushes a blank screen and leaves the repaint to the
next flush, so every pane toggle blinked the whole interface.
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 · 160 lines · 0 tokens per session scan A e4215e43f240
thurbox-performance is a skill published in the GitHub repository Thurbeen/thurbox (57 stars, last pushed 2d ago), licensed MIT. It adds 106 tokens to every session and 2,730 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.