Borrowing it
Nothing to install: this file belongs to Thurbeen/thurbox. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Thurbeen/thurbox/main/.agents/skills/thurbox-cli/SKILL.mdgit 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-cli)<a href="https://agentmods.dev/skills/thurbeen/thurbox/thurbox-cli"><img src="https://agentmods.dev/badge/skills/thurbeen/thurbox/thurbox-cli/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/thurbeen/thurbox/thurbox-cli"><img src="https://agentmods.dev/badge/skills/thurbeen/thurbox/thurbox-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Tool Misuse · line 139 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Rogue Agent · line 414 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.1 | $0.00000 | $0.18613 |
| Opus 5.5 | $0.00000 | $0.07445 |
| Sonnet 5.5 | $0.00000 | $0.03723 |
| Haiku 4.5 | $0.00000 | $0.01861 |
Grade A, and why
thurbox-cli 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 yesterday.
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 — 1,143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
thurbox-cli, automations, tasks and messages
Working reference indexed by AGENTS.md. 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.
thurbox-cli
A second binary (thurbox-cli) drives the same SQLite-backed,
tmux-hosted sessions headlessly (no TUI). It shares the database
with the TUI; changes appear via PRAGMA data_version polling.
cargo build --bin thurbox-cli
thurbox-cli session create --name demo --repo-path /path \
--agent codex --worktree-branch feat/x
# Spawn on a remote host from hosts.toml (worktree + tmux live remotely):
thurbox-cli session create --name demo --repo-path /srv/repo \
--host devbox --worktree-branch feat/x
# Spawn a worker under a lead session (parent must exist):
thurbox-cli session create --name worker --repo-path /path \
--parent <lead-uuid>
# Multi-repo: each --add-repo gets its own worktree on --worktree-branch;
# --add-dir attaches a repo as-is (no branch). The agent launches in a
# symlink workspace gathering every repo. Works on `task create` too.
thurbox-cli session create --name demo --repo-path /a \
--agent claude --worktree-branch feat/x \
--add-repo /b@main --add-repo /c@master --add-dir /reference
thurbox-cli session list # human-readable table
thurbox-cli session list --json | jq # machine output for scripts
thurbox-cli session list --parent <lead-uuid> --json | jq # direct children only
thurbox-cli session list --parent <lead-uuid> --recursive # every descendant
thurbox-cli session list --tree # nested as the sidebar nests it
Subcommands: ui (instances/state/actions/action/input for a live local TUI),
schema (CLI command tree plus that instance's live UI action catalog),
agent (launch-args — see below), session (create/list [--deleted [--since]]/get/delete/reap/purge/restore/restart
[--if-missing]/rename/reparent/stop/start/fork/exec/meta/reports-as/set-key/send [--no-enter]/key/capture/focus/signal/doctor/sync/revision/register —
sync/revision/register and the flags serve session sharing, ADR-24), watch (stream
the session event log, one event per line), runtime (status/stop — what
thurbox runs that is not a session), automation (alias auto:
create/list/show/edit/remove/run/runs/tick), task (alias todo:
create/list/show/edit/remove/run), message (alias msg:
send/inbox/prune — the inter-session mailbox queue; see below), editor
(get/set the Ctrl+O editor command; editor mode <auto|terminal|gui> chooses
how it launches — terminal editors get a real TTY via a tmux popup or TUI
suspend, GUI editors spawn detached; see the Editor Integration section of
docs/FEATURES.md), config
(validate/show — strict-parses every config file / prints the
effective resolved config; see docs/CONFIG.md), extension
(alias ext: install/uninstall/reinstall/list/available/update/activate/
deactivate/status — manage opt-in extensions; see below), version
(prints the running version; --check queries GitHub's latest release —
gated on [features] version_check, on by default for 1.0), update
(downloads, verifies, and replaces the installed binaries with the latest
release within the current major — a new major is reported, never installed,
because 2.x replaced the whole interface; --force bypasses the
up-to-date/dev-build/major guards; gated on
[features] auto_update, on by default for 1.0; the TUI also runs this silently on
startup when the flag is on), notify
(diagnose OS desktop notifications: prints the detected delivery backend
and last error; --test fires a sample; send --title --body [--session] [--key --min-interval] delivers one for a script, hook or Exec automation —
honours both off switches, never touches session state, dedupes a key across
processes through a lease in event_cursors; see docs/CONFIG.md →
Scripted notifications), perf
(print the perf snapshot a running TUI publishes while THURBOX_PERF_LOG
or its perf HUD is active; --plugins for one row per pane, sorted by cost,
with hints — see docs/PERFORMANCE.md), plugin
(interface plugins without a TTY: dir reports the directory in force and
which of the two rules chose it, new <name> writes a starter that already
loads, check loads the interface the way thurbox does and exits non-zero on
a failure — including on a pane that loaded but which no arrangement places,
printing the layout.lua line to add — list is the same inventory the settings
modal's Interface tab shows, and
events lists every event a plugin may subscribe to with its payload, and
install|sync|update|remove|available manage panes from a declarative spec
— see docs/PLUGINS.md), doctor
(whether this machine has what a session needs: the multiplexer and its
version, every registered agent's command, the launcher for each configured
host, and the full search path. The companion to session doctor, which asks
whether an existing session's status hooks are wired — this one names no
session, so it answers on a machine where nothing has been created yet. fail
and a non-zero exit only for what must work: no multiplexer, or no registered
agent that resolves anywhere; a partly-installed registry is warn and exits 0.
See "What is missing, before you hit it" below).
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.
- yesterday Changed · +1 lines 7cd379d67a33
- 5d ago Changed · +40 lines c1897911287f
- 7d ago Changed · +8 lines f1d1635828a4
- 8d ago Changed · +10 lines 46408a5ed995
- 9d ago Changed · +49 lines 6ca5bf392652
- 10d ago Changed · +9 lines 1ee1f9684ab1
- 11d ago Changed · +51 lines 469fcefa3134
- 12d ago Changed · +19 lines 39a9057f1aec
- 13d ago Changed · +3 lines 75a486234a26
- 17d ago First seen · 953 lines · 0 tokens per session scan A abd8b5dfa165
thurbox-cli is a skill published in the GitHub repository Thurbeen/thurbox (115 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 18,613 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…