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/jukanntenn/glm-plan-usage/releasenpx skills add jukanntenn/glm-plan-usage --skill releasegit clone --depth 1 https://github.com/jukanntenn/glm-plan-usageWrote 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.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.00087 | $0.01326 |
| Opus 5 | $0.00044 | $0.00663 |
| Sonnet 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 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.
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.
- 4d 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 (13 stars, last pushed 2mo ago), licensed MIT. It adds 87 tokens to every session and 1,326 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
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.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…