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-releasenpx skills add Thurbeen/thurbox --skill thurbox-releasegit 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-release)<a href="https://agentmods.dev/skills/thurbeen/thurbox/thurbox-release"><img src="https://agentmods.dev/badge/skills/thurbeen/thurbox/thurbox-release.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.00097 | $0.03169 |
| Opus 5 | $0.00048 | $0.01584 |
| Sonnet 5 | $0.00019 | $0.00634 |
| Haiku 4.5 | $0.00010 | $0.00317 |
Grade B, and why
thurbox-release scanned grade B with 2 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 4d 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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/Thurbeen/thurbox/main/scripts/install.sh | sh Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/Thurbeen/thurbox/main/scripts/install.sh | sh How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thurbox releases, packaging and installers
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.
Release Process
Releases are fully automated via GitHub Actions. No version commits are created - version is determined by git tags only.
How It Works
Every push to main automatically triggers the release workflow:
- Commit Analysis: Analyzes all commits since last tag using cocogitto
- Release Decision — a release needs both gates to pass:
- Commit type (
check-release'sparsestep): commits must includefeat,fix, orperf. Only docs/chore/ci commits → no release. - Artifact relevance (
check-release'sshippedstep): the diff since the last tag must touch something a user installs (src/,tests/,ui/,examples/,build.rs,Cargo.toml/Cargo.lock,rust-toolchain.toml,Cross.toml,extensions/,packaging/,scripts/install.{sh,ps1},cd.yml).extensions/andexamples/panes/are there although no binary carries them: a bare-name install resolves against the release tag, so a change never tagged is one nobody can install.ui/andexamples/lua/are there more directly still — both areinclude_str!d into the binary, so they are bytes a user installs. Commit type alone over-releases: Renovate labels a GitHub-Actions pin bumpfix(deps)and the website is versionedfeat(ui)/fix(ui), so a CSS-only or lint-action-only change used to cut a real release (v1.2.13 through v1.3.0 were four website-only releases, one a minor) — burning a 4-platform build and pushing to the moderated Chocolatey/winget channels for a no-op binary. Such commits stay in history and ride along in the next real release's changelog. - The gate is evaluated over the whole span since the last tag, not the
single push, so a website-only push landing on an unreleased
src/commit still cuts the release it owes. A forcedworkflow_dispatchversion skips the relevance gate — an explicit human cut is always honoured.
- Commit type (
- Automated Release (if needed):
- Determines semantic version (feat→minor, fix/perf→patch, breaking→major)
- Creates lightweight git tag:
v{version}(e.g., v1.0.0) - Pushes tag to origin
- Builds binaries for 4 platforms (3 Unix
.tar.gz+ 1 Windows.zip; version passed via environment variable) - Generates changelog from commits
- Publishes GitHub Release with binaries and release notes
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.
- 4d ago First seen · 204 lines · 0 tokens per session scan B 3fbef2fc2940
thurbox-release is a skill published in the GitHub repository Thurbeen/thurbox (57 stars, last pushed 4d ago), licensed MIT. It adds 97 tokens to every session and 3,169 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
reachy-mini-release-notes
Generate Reachy Mini (reachymini) release notes from cached PR JSON files. Use when asked to draft release notes from PR files.
release
Cut a sim-use release end-to-end. Use when the user runs /release or asks to "ship a release", "publish a version", "cut a release", or "release to homebrew". Drives scripts/local-release.sh; never reimplement its build/sign/tarball logic.
snapshot-release
Drives the snapshot-release flow for the current branch's PR. Posts a /snapshot comment on the PR if one isn't already there (with confirmation), waits for the Continuous Releases workflow to finish, and reports the tarball URLs from the resulting 📦 Snapshot Release comment. Use for both triggering and waiting …
release-notes
Generate GitHub release notes for the Membrane api-gateway repo by collecting the commits between the last release and master, grouping them into Features / Improvements / Fixes / Security / Dependencies, and linking each to its PR. Use whenever the user wants to draft, extract, or write release notes / a changelog /…