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/hyperaiteam/clitrigger/releasenpx skills add HyperAITeam/CLITrigger --skill releasegit clone --depth 1 https://github.com/HyperAITeam/CLITriggerWhat 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.00033 | $0.01872 |
| Opus 5 | $0.00016 | $0.00936 |
| Sonnet 5 | $0.00007 | $0.00374 |
| Haiku 4.5 | $0.00003 | $0.00187 |
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 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Bump package.json version, commit, and create a git tag for npm release.
Current context
- Current branch:
!git branch --show-current - Working tree status:
!git status --short - Current version:
!node -p "require('./package.json').version" - Recent tags:
!git tag --sort=-v:refname | head -5
Instructions
Follow these phases exactly, in order.
Phase 1: Validation
-
Branch check: Must be on
main(ormaster). If not, stop and tell the user. -
Clean working tree: Run
git status --porcelain. If there are uncommitted changes, stop and tell the user to commit or stash first. -
Parse argument:
- If `` is
patch,minor, ormajor: calculate the next version from the current version using semver rules. - If `` is an explicit version (e.g.,
1.2.3): use it directly. Validate it's a valid semver string. - If `` is empty or not provided: default to
patch.
- If `` is
-
Duplicate check: Verify the target version tag (
v<version>) does not already exist. If it does, stop and tell the user.
Phase 2: Version bump
-
Update
package.json: Change the"version"field to the new version. -
Update
package-lock.json: Runnpm install --package-lock-onlyto sync the lockfile version without installing packages.
Phase 3: 릴리즈 노트 작성
docs/release-notes/v<new-version>.md에 영어로 릴리즈 노트를 작성한다 (GitHub Release는 영어권 사용자 대상 — 한국어로 쓰지 말 것. 단, 전체 커밋 목록의 커밋 메시지는 원문 그대로 둔다). push 후 GitHub Actions(.github/workflows/release.yml)가 태그 체크아웃 tree에서 이 파일을 읽어 GitHub Release body로 사용한다 (파일이 없으면 자동 PR 인덱스로 폴백).
이 phase에서는 파일만 작성하고 commit하지 않는다. 다음 Phase 4가 release 커밋에 노트 파일을 함께 stage 해서 태그가 노트를 포함한 커밋을 가리키도록 한다.
3-1. 직전 태그 결정
git tag --sort=-v:refname | head -1
- 결과가 비어 있으면 첫 릴리즈로 간주하고 노트 본문에 "초기 릴리즈" 명시. 커밋 범위는 첫 커밋부터 HEAD까지.
- 결과가 있으면
<PREV_TAG>변수로 사용. Phase 1에서 새 태그 중복 체크가 끝났으므로 항상 새 태그보다 이전.
3-2. 변경 재료 수집
다음 두 가지를 모아 한 번에 본다:
- 커밋 인덱스:
git log <PREV_TAG>..HEAD --pretty=format:"%h %s" - changelog entry 묶음:
<PREV_TAG>커밋의 author date(git log -1 --format=%ad --date=short <PREV_TAG>)부터 오늘까지의docs/changelog/YYYY-MM/YYYY-MM-DD*.md파일 모두 읽기.- 이미 한국어로 큐레이션된 본문이 있으므로 release 노트는 이걸 영어로 요약/재구성하는 데 집중. 통째 복붙·직역 금지.
- changelog entry가 0개면(짧은 패치 릴리즈) 커밋 메시지 + 핵심 diff만 보고 직접 작성.
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 · 184 lines · 33 tokens per session scan A 886f58cad34d
release is a skill published in the GitHub repository HyperAITeam/CLITrigger (13 stars, last pushed 8d ago), licensed MIT. It adds 33 tokens to every session and 1,872 once invoked, about $0.0002 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
gh-pr-merge-unstable-state-needs-auto-and-watch-branch-deletes
Diagnose and recover from two adjacent gh pr merge failure modes that masquerade as merge conflicts. Use when: (1) gh pr merge --squash (or --merge) errors with "To have the pull request merged after all the requirements have been met, add the --auto flag" AND "Run the following to resolve the merge conflicts locally"…
swarmux-release-playbook
Execute and verify GitHub Releases for this repo. Use when the user asks to cut a release, publish artifacts, trigger release workflow, or check why a release did not publish.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
release
Release pipeline for CLI, mobile, web, and server. Guides through version bumping, building, testing, publishing, and deploying. Replaces the old interactive release-it flow with a Claude Code-native experience. Use when user types /release or asks to release, publish, deploy, or ship any component.
cut-release
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR…
versioning-policy
SemVer rules for Squad's stable, preview, insider, and local package versions.