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/amxv/agentbox/agentbox-cli-releasenpx skills add amxv/agentbox --skill agentbox-cli-releasegit clone --depth 1 https://github.com/amxv/agentboxWhat 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.00077 | $0.02426 |
| Opus 5 | $0.00039 | $0.01213 |
| Sonnet 5 | $0.00015 | $0.00485 |
| Haiku 4.5 | $0.00008 | $0.00243 |
Grade A, and why
agentbox-cli-release 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentbox CLI Release
Release the Go CLI and its npm wrapper as one versioned unit. Use GitHub Actions by default. Use the manual fallback only when the publish job is cancelled before any step runs because GitHub cannot assign a hosted runner.
Release contract
- Repository:
https://github.com/amxv/agentbox - Go CLI version:
internal/agentbox/version/version.go - npm wrapper version:
packaging/cli/package.json - npm package:
@amxv/agentbox - Release tag:
agentbox-cli-vX.Y.Z - Publish workflow:
.github/workflows/publish-agentbox-npm.yml - Release commit:
chore: release agentbox cli X.Y.Z
The dashboard has its own private package under apps/dashboard; do not change its version for CLI releases. The preparation script requires the Go and npm CLI versions to match.
The generated files under packaging/cli/vendor/ are ignored build artifacts and
must not be committed.
The publish workflow runs CLI tests, builds five binaries, packs and publishes
the npm package with the NPM_TOKEN repository secret, and creates a GitHub
Release for tag pushes matching agentbox-cli-v*. The expected release assets
are:
agentbox-X.Y.Z-darwin-arm64.tar.gzagentbox-X.Y.Z-darwin-amd64.tar.gzagentbox-X.Y.Z-linux-arm64.tar.gzagentbox-X.Y.Z-linux-amd64.tar.gzagentbox-X.Y.Z-windows-amd64.zipamxv-agentbox-X.Y.Z.tgz
Standard GitHub Actions flow
1. Preflight
Work from a clean main checkout. Preserve unrelated user changes and stop if
the checkout is dirty or has diverged.
git status --short --branch
git fetch origin --tags
git pull --ff-only origin main
git tag --list 'agentbox-cli-v*' --sort=-version:refname | head -20
gh release list --repo amxv/agentbox --limit 10
node -p "require('./packaging/cli/package.json').version"
npm view @amxv/agentbox version dist-tags --json
Choose the next semantic version from the current source change. Confirm that the tag and npm version do not already exist. Before changing versions, inspect the CLI source and tests relevant to the release, then run the release checks:
What ships with it
1 file 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.
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 · 228 lines · 77 tokens per session scan A 3e572305e607
agentbox-cli-release is a skill published in the GitHub repository amxv/agentbox (1 stars, last pushed 5d ago), licensed Apache-2.0. It adds 77 tokens to every session and 2,426 once invoked, about $0.0004 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-31.
Other skills, from other repositories
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
release-jetbrains
Use when releasing the Kilo JetBrains plugin -- resolve a version ("next rc" or explicit), run the prepare workflow, edit and commit a filtered human-readable changelog on the release PR, then watch publish to completion.
deepchat-release
Prepare and publish DeepChat releases in this repository. Use when Codex needs to bump the app version, update CHANGELOG.md, keep release notes bilingual from v1.0.1 onward with English bullets first and Chinese bullets second, run release checks, create or update versioned release branches such as release/v1.0.1…
changeset-pr
Create or update a .changeset/.md file for the current branch or PR in this repository, choose the correct package scope and release type, and verify the result against repo-specific Changesets config. Use when a publishable package changed, when a PR is missing a changeset, when an existing changeset needs…
release
Prepare, validate, and publish a Pake release. Not for version bumps without release intent.
github-ops
GitHub issue, PR, and release operations via gh CLI. Not for code review or release builds.