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-session-statusnpx skills add Thurbeen/thurbox --skill thurbox-session-statusgit clone --depth 1 https://github.com/Thurbeen/thurboxWrote 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/thurbeen/thurbox/thurbox-session-status)<a href="https://agentmods.dev/skills/thurbeen/thurbox/thurbox-session-status"><img src="https://agentmods.dev/badge/skills/thurbeen/thurbox/thurbox-session-status.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00000 | $0.04252 |
| Opus 5 | $0.00000 | $0.02126 |
| Sonnet 5 | $0.00000 | $0.00850 |
| Haiku 4.5 | $0.00000 | $0.00425 |
Grade A, and why
thurbox-session-status 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 today.
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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thurbox session status and notifications
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.
Session status (hooks-driven)
The session list shows, at a glance, which agents are blocked, working,
or done. SessionState (src/session/hook_status.rs) is the whole
vocabulary — one enum, every surface. Four of its words are the agent's own
hook report; the rest are thurbox's own, and each is spelled apart from idle
on purpose, because collapsing "nothing here is wired to report" or "the host
is gone" into "the agent says it is at rest" is exactly the conflation the
module exists to prevent:
| State | Colour | Glyph | Meaning |
|---|---|---|---|
working |
yellow | animated braille spinner (⠋⠙⠹…; static ◐) |
agent is actively running (hook) |
blocked |
red | ◆ |
agent needs input or approval (hook) |
done |
blue | ● (filled) |
a turn just finished; shown until you switch away (hook) |
idle |
green | ○ (hollow) |
acknowledged (you moved off a Done), never active, or at rest |
unreachable |
muted grey | ⊘ |
remote host down/offline; the ordinary row, derived from a live attach failure, awaiting reconnect |
stopped |
— | — | parked by session stop: no process at all, which is why it outranks whatever the hook columns still hold |
running |
— | — | an agent holds the pane and nothing has signalled — an observation, never a claim about what it is doing |
uncovered |
— | — | this agent is wired to report nothing, so its silence means nothing |
unreported |
— | — | the agent can report and has not yet |
The last four carry no dot: the interface can always observe quiescence and
reachability and knows the park mark from the row, so its rows resolve to the
first five. The others are what a headless surface answers when a fact the
interface has is one it cannot observe. The Error state v1 reserved for a
crashed agent is gone with SessionStatus: it was never derived (process exit
carries no failure signal), and a word no surface can produce is one more thing
for a driver to handle for nothing.
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.
- today Changed · +49 lines 47770dd1887f
- 4d ago First seen · 196 lines · 0 tokens per session scan A 1a74aa8d9404
thurbox-session-status is a skill published in the GitHub repository Thurbeen/thurbox (60 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,252 tokens. 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.
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.
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.
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…