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/kc0506/ntucool/releasingnpx skills add kc0506/ntucool --skill releasinggit clone --depth 1 https://github.com/kc0506/ntucoolWrote 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/kc0506/ntucool/releasing)<a href="https://agentmods.dev/skills/kc0506/ntucool/releasing"><img src="https://agentmods.dev/badge/skills/kc0506/ntucool/releasing.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.00099 | $0.01855 |
| Opus 5 | $0.00049 | $0.00928 |
| Sonnet 5 | $0.00020 | $0.00371 |
| Haiku 4.5 | $0.00010 | $0.00186 |
Grade C, and why
releasing scanned grade C with 2 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 5d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- **`cool update` available since v0.0.3.** The embedded `axoupdater` reads an install-receipt that cargo-dist's shell/powershell installer drops at `$XDG_CONFIG_HOME/ntucool/ntucool-receipt.json`. Users on v0.0.2 or old Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **`cool update` available since v0.0.3.** The embedded `axoupdater` reads an install-receipt that cargo-dist's shell/powershell installer drops at `$XDG_CONFIG_HOME/ntucool/ntucool-receipt.json`. Users on v0.0.2 or old How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releasing ntucool
ntucool ships two artifacts on every release that have independent version sources in the repo:
| Artifact | Version source | Distribution channel | Trigger |
|---|---|---|---|
cool binary |
[workspace.package] version in root Cargo.toml (+ 3 internal path-dep pins) |
GitHub Release via cargo-dist | git push <tag> matching v* |
| Claude Code plugin | version in plugins/ntucool/.claude-plugin/plugin.json |
Claude Code's plugin update reads marketplace.json from origin/main and diffs plugin.json versions |
git push origin main |
Both must bump for a release to flow end-to-end. Skipping the plugin bump is a silent failure — Claude Code's plugin update won't notice anything changed (it keys on plugin.json version, not git tags).
Pre-flight (run before bumping)
cargo test --workspace --quiet
cargo check -p ntucool --quiet
Quick MCP smoke (kept in scripts/):
cargo build --release -p ntucool --quiet
(printf '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"smoke","version":"0"}}}\n{"jsonrpc":"2.0","method":"notifications/initialized"}\n{"jsonrpc":"2.0","id":2,"method":"tools/list"}\n'; sleep 0.5) \
| timeout 5 ./target/release/cool mcp 2>/dev/null \
| grep -o '"name":"[^"]*"' | wc -l # expect ≥ 24
Tag the current expected tool count somewhere and treat a deviation as a regression — past releases settled at 24 - 25.
The bump matrix (5 lines, in 4 files)
Same OLD → NEW substitution everywhere:
Cargo.toml: [workspace.package] version
cool-cli/Cargo.toml (2 lines): path-dep pins to cool-api, cool-tools
cool-tools/Cargo.toml: path-dep pin to cool-api
cool-tui/Cargo.toml: path-dep pin to cool-api
plugins/ntucool/.claude-plugin/plugin.json: version
One-liner that bumps all five at once (verify the match list first):
OLD=0.0.2 NEW=0.0.3
sed -i "s/version = \"$OLD\"/version = \"$NEW\"/g" \
Cargo.toml cool-cli/Cargo.toml cool-tools/Cargo.toml cool-tui/Cargo.toml
sed -i "s/\"version\": \"$OLD\"/\"version\": \"$NEW\"/" plugins/ntucool/.claude-plugin/plugin.json
cargo check -p ntucool --quiet # touches Cargo.lock
git diff --stat
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.
- 5d ago First seen · 118 lines · 99 tokens per session scan C 60ab0f9f1c46
releasing is a skill published in the GitHub repository kc0506/ntucool (10 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 1,855 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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
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…