Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jukanntenn/glm-plan-usagenpx agentmods add skills/jukanntenn/glm-plan-usage/releaseWrote 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/jukanntenn/glm-plan-usage/release)<a href="https://agentmods.dev/skills/jukanntenn/glm-plan-usage/release"><img src="https://agentmods.dev/badge/skills/jukanntenn/glm-plan-usage/release/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/jukanntenn/glm-plan-usage/release"><img src="https://agentmods.dev/badge/skills/jukanntenn/glm-plan-usage/release.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00087 | $0.01326 |
| Opus 5.5 | $0.00035 | $0.00530 |
| Sonnet 5.5 | $0.00017 | $0.00265 |
| Haiku 4.5 | $0.00009 | $0.00133 |
Grade A, and why
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 2mo 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Process
Safe release workflow for glm-plan-usage (Rust CLI, multi-platform NPM package). Every step validates before proceeding; failures report the problem + suggestion then STOP — never auto-fix.
Prerequisites
Verify clean tree and identify current state:
git status # must be clean
grep '^version = ' Cargo.toml # current version
git describe --tags --abbrev=0 # last tag
Steps 1-5: Automated Phase
Step 1: Quality Checks
cargo test && cargo fmt -- --check && cargo clippy -- -D warnings
Fail → report which check failed (test/fmt/clippy) + likely cause, STOP.
Step 2: Version Bump
- Show commits since last tag:
git log --oneline <last_tag>..HEAD - Ask user to confirm new version (suggest semver bump: patch=fixes, minor=features, major=breaking)
- Update exactly TWO files:
Cargo.toml:version = "x.y.z"npm/main/package.json:"version": "x.y.z"
- Sync
Cargo.lockwith the new version:cargo check - Verify all three files show the same new version (
Cargo.toml,npm/main/package.json,Cargo.lock)
Do NOT touch npm/platforms/*/package.json or optionalDependencies in npm/main/package.json — prepare-packages.js handles those at release time.
Step 3: Local Build
cargo build --release
Fail → report error + likely cause, STOP. Pass → target/release/glm-plan-usage exists.
Step 4: Local Publish Verification
NPM_REGISTRY=http://192.168.5.50:4873/ ./npm/publish-local.sh
This reads version from Cargo.toml, runs prepare-packages.js, copies binaries, publishes all packages to local verdaccio. Missing cross-compile binaries are expected (only current platform builds locally).
Fail → report which platform failed + error output, STOP.
Step 5: Update CHANGELOG & Verify READMEs
CHANGELOG: git log --oneline <last_tag>..HEAD → derive user-visible changes, draft entry matching existing format, present to user for review, then insert at TOP:
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.
- 2mo ago First seen · 168 lines · 87 tokens per session scan A d4d9a7019cfb
release is a skill published in the GitHub repository jukanntenn/glm-plan-usage (14 stars, last pushed 4mo ago), licensed MIT. It adds 87 tokens to every session and 1,326 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
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.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.