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/851-labs/tokenmaxxing/release-clinpx skills add 851-labs/tokenmaxxing --skill release-cligit clone --depth 1 https://github.com/851-labs/tokenmaxxingWhat 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.00073 | $0.01121 |
| Opus 5 | $0.00036 | $0.00561 |
| Sonnet 5 | $0.00015 | $0.00224 |
| Haiku 4.5 | $0.00007 | $0.00112 |
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 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 — 146 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.
Pre-flight Checks
Verify main is clean and current.
git status --short --branch
git branch --show-current
git pull origin main
If the working tree has unrelated changes, stop and ask before staging or committing.
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.
$EDITOR apps/cli/package.json
bun install --lockfile-only
node -p "JSON.parse(require('node:fs').readFileSync('apps/cli/package.json', 'utf8')).version"
Use the printed version as X.Y.Z below.
Step 2: Update Changelog
Update CHANGELOG.md before running checks.
- Move the relevant
Unreleasedentries into a new## X.Y.Z - YYYY-MM-DDsection. - Keep a fresh empty
## Unreleasedsection at the top. - Keep entries concise and user-facing; do not paste raw commit logs.
- Include all notable CLI changes in the release section. Include web/API changes only when they shipped since the previous CLI release and are user-visible or operationally important.
Use today's date in YYYY-MM-DD format.
Step 3: Run Checks
Run the existing checks directly.
bun --filter @851-labs/tokenmaxxing typecheck
bun --filter @851-labs/tokenmaxxing test
bun run lint
bun run fmt
bun --filter @851-labs/tokenmaxxing build
bun --filter @851-labs/tokenmaxxing build:native-packages --single
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 · 146 lines · 73 tokens per session scan A f977440c6701
release-cli is a skill published in the GitHub repository 851-labs/tokenmaxxing (67 stars, last pushed 27d ago), licensed MIT. It adds 73 tokens to every session and 1,121 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-30.
Other skills, from other repositories
owndiff-pre-commit
Audit OwnDiff changes before committing or releasing by checking scope, generated artifacts, private data, documentation accuracy, version consistency, structured files, tests, and the OwnDiff ownership gate. Use when a user asks to verify, clean up, prepare, commit, publish, or release changes in the OwnDiff…
ship
Build, commit, push & version bump workflow - automates the complete release cycle.
repo-recap
Generate a comprehensive repo recap (PRs, issues, releases) for sharing with team. Pass "en" or "fr" as argument for language (default fr).
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.
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, and create a PR. Use for an explicit /ship invocation or when the user requests the full ship, release, or deploy workflow. For an ordinary commit, push, or pull-request publishing request, use the built-in…
om-auto-update-changelog
Open Mercato releases must keep CHANGELOG.md, UPGRADENOTES.md, and version-specific downstream migration skills aligned. Apply this contract after the external skill resolves {version}, {date}, and the previous changelog release, but before it edits files or delegates to om-auto-create-pr.