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/seokan-jeong/team-shinchannpx agentmods add commands/seokan-jeong/team-shinchan/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/commands/seokan-jeong/team-shinchan/release)<a href="https://agentmods.dev/commands/seokan-jeong/team-shinchan/release"><img src="https://agentmods.dev/badge/commands/seokan-jeong/team-shinchan/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/commands/seokan-jeong/team-shinchan/release"><img src="https://agentmods.dev/badge/commands/seokan-jeong/team-shinchan/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.00025 | $0.01236 |
| Opus 5 | $0.00013 | $0.00618 |
| Sonnet 5 | $0.00005 | $0.00247 |
| Haiku 4.5 | $0.00003 | $0.00124 |
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 10d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Command
Bumps the version across the 4 required files and — when asked — runs the full
GitHub release flow (commit + tag + push + GitHub Release). Implemented in
src/release.js.
The 4-file version bump is always performed. The git/GitHub steps are
opt-in (--full, or individual flags) so a bump can be reviewed before any
history is written.
Usage
node src/release.js <X.Y.Z> [flags]
# or, as the slash command:
/team-shinchan:release --version <X.Y.Z> [flags]
| Flag | Effect |
|---|---|
--dry-run |
Preview every step; no file writes, git, or gh. |
--notes-file <f> |
Release-notes source for the CHANGELOG body and the GitHub Release body. If omitted, notes are drafted from git log <last-tag>..HEAD (never a silently-empty header). |
--title <str> |
GitHub Release title (default vX.Y.Z). |
--git |
Stage the 4 files + commit chore: release vX.Y.Z. |
--tag |
Annotated tag vX.Y.Z (implies --git). |
--push |
Push the current branch + tag to origin (implies --git). |
--gh-release |
Create a GitHub Release via gh (implies --tag). |
--full |
--git --tag --push --gh-release. |
--allow-dirty |
Skip the clean-working-tree guard. Lets a release proceed with uncommitted feature work in the tree — the release commit still stages ONLY the 4 version files, so the tag will NOT contain those changes. Use only for an intentional bump-only commit. |
Examples
# Bump only — review the diff, then release manually.
node src/release.js 4.39.0 --dry-run
node src/release.js 4.39.0
# Full release in one shot, with hand-written notes.
node src/release.js 4.39.0 --full --notes-file RELEASE_NOTES.md --title "v4.39.0 — Big Feature"
# Preview exactly what --full would run (no side effects).
node src/release.js 4.39.0 --full --dry-run
What it updates
| File | Field |
|---|---|
.claude-plugin/plugin.json |
"version" |
.claude-plugin/marketplace.json |
plugins[0].version |
README.md |
Version badge (version-X.Y.Z-blue) |
CHANGELOG.md |
New ## [X.Y.Z] - <date> section (filled from notes) |
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.
- 10d ago First seen · 102 lines · 25 tokens per session scan A 805eaf4fdb54
release is a command published in the GitHub repository seokan-jeong/team-shinchan (8 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 1,236 once invoked, about $0.0001 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-31.
Other commands, from other repositories
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
release
Release a new version. Bumps version, updates docs/site/changelog, tags, pushes, and updates the marketplace repo.
release
Invoke Eva (Release) to cut a versioned GitHub Release from main, or backfill historical releases. Routes the version-bump commit through a PR (branch protection-friendly) and uses full 40-char SHAs with gh release create to avoid the silent short-SHA rejection.
release
Release a new version of claude-mpm (MPM-provided — may be shadowed by a user /release command).
ship
Ship workflow — detect base branch, merge, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR.
document-release
Post-ship documentation update — reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped.