Borrowing it
Nothing to install: this file belongs to 851-labs/tokenmaxxing. 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/851-labs/tokenmaxxing/main/.agents/skills/release-cli/SKILL.mdgit clone --depth 1 https://github.com/851-labs/tokenmaxxingWrote 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/851-labs/tokenmaxxing/release-cli)<a href="https://agentmods.dev/skills/851-labs/tokenmaxxing/release-cli"><img src="https://agentmods.dev/badge/skills/851-labs/tokenmaxxing/release-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/851-labs/tokenmaxxing/release-cli"><img src="https://agentmods.dev/badge/skills/851-labs/tokenmaxxing/release-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00078 | $0.03165 |
| Opus 5.5 | $0.00031 | $0.01266 |
| Sonnet 5.5 | $0.00016 | $0.00633 |
| Haiku 4.5 | $0.00008 | $0.00316 |
Grade A, and why
release-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 28d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI Release Process
Follow these steps to release a new version of the @851-labs/tokenmaxxing CLI. Only perform mutating release actions when the user explicitly asks to release or publish a new CLI version.
npm versions are immutable and a pushed cli-v* tag may already have published packages, so a version is spent once its tag reaches origin. Never move or re-point a pushed tag to different code; see Publish Workflow Fails After Tag Push.
Pre-flight Checks
Release from a fresh worktree off origin/main, never from the user's main checkout. The lefthook pre-commit hook runs bun run check and bun run test over the whole checkout, so unrelated untracked files there (for example an outputs/ folder) can fail the release commit. Do not work around that with --no-verify or by touching unrelated files.
git fetch origin main --tags
release_dir="$(mktemp -d)/tokenmaxxing-release"
git worktree add --detach "$release_dir" origin/main
cd "$release_dir"
bun install --frozen-lockfile
git status --short
git status --short must print nothing. After choosing the version in Step 1, confirm it is unused on npm and in git. Each command below must print nothing:
npm view @851-labs/[email protected] version 2>/dev/null
git ls-remote --tags origin cli-vX.Y.Z
If either prints something, the version is taken: pick the next one, or see Tag Already Exists.
Step 1: Choose And Bump Version
Decide the bump from the requested change scope: patch, minor, major, or a prerelease variant when explicitly requested.
Update only apps/cli/package.json for the new version unless the lockfile changes after install. Do not add generated native packages to the source workspace; release publishing generates those package manifests from the CLI version. For alpha/beta/rc releases, use a prerelease version such as X.Y.Z-alpha.0; the publish script derives the npm dist-tag from the prerelease identifier unless --tag is passed explicitly.
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.
- 28d ago Changed · +30 lines · +5 tokens per session 9b7afc38c5fb
- 29d ago Changed · +68 lines 9e6422c3ce09
- 1mo ago Changed · -2 lines 69ada08f762a
- 1mo ago First seen · 146 lines · 73 tokens per session scan A f977440c6701
release-cli is a skill published in the GitHub repository 851-labs/tokenmaxxing (84 stars, last pushed 4d ago), licensed MIT. It adds 78 tokens to every session and 3,165 once invoked, about $0.0003 per session on Opus 5.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
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
git-workflow
Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…
contributing
Codex adapter for the opencode-swarm contribution checklist. Use when preparing user-visible changes, release note fragments, local validation, branch hygiene, PR checklist items, or contribution-policy compliance before publishing work.
finishing-a-development-branch
Use when implementation is complete, tests pass, and you need to decide the integration path. Also use when asked to prepare a branch for release: 'update changelog', 'bump version', 'bump patch version', 'make sure changelog is correct', 'make sure version is correct'. Triggers: 'done with this branch', 'ready to…
git-release
Draft release notes from merged PRs, propose a semver bump, and emit a copy-pasteable gh release create command. Use when preparing a tagged GitHub release.
git-github-flow
Use for branch prep, clean commits, PR descriptions, GitHub issue triage, changelogs, release notes, review response, merge readiness, or publishing a branch safely.