Borrowing it
Nothing to install: this file belongs to akiojin/llmlb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/akiojin/llmlb/develop/.codex/skills/release/SKILL.mdgit clone --depth 1 https://github.com/akiojin/llmlbWrote 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/akiojin/llmlb/release)<a href="https://agentmods.dev/skills/akiojin/llmlb/release"><img src="https://agentmods.dev/badge/skills/akiojin/llmlb/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/akiojin/llmlb/release"><img src="https://agentmods.dev/badge/skills/akiojin/llmlb/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.00052 | $0.01057 |
| Opus 5.5 | $0.00021 | $0.00423 |
| Sonnet 5.5 | $0.00010 | $0.00211 |
| Haiku 4.5 | $0.00005 | $0.00106 |
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 8d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Workflow
LLM主導でバージョン更新とリリースコミットを作成し、ワークフローでタグ・Release・配布を完了する。
Preflight
gh auth statusが成功することgit status --shortが空であることorigin/developを最新化できること
フロー
release (/release) 実行
↓
① origin/develop を pull してローカルを最新化
↓
② バージョン更新(Cargo.toml, CHANGELOG.md)
↓
③ chore(release): vX.Y.Z コミット作成
↓
④ Closing Issue を収集
↓
⑤ develop → main マージ(PR本文に Closing Issues 記載)
↓
⑥ release.yml がタグ作成 → GitHub Release作成
↓
⑦ publish.yml がバイナリビルド → Release にアタッチ
手順
0. ローカルを最新化(必須)
git fetch origin
git pull origin develop
1. バージョン更新
[workspace.package]
version = "X.Y.Z"
2. CHANGELOG.md 更新
## [X.Y.Z] - YYYY-MM-DD
### Added
- 新機能の説明
### Fixed
- バグ修正の説明
3. リリースコミット作成
git add Cargo.toml Cargo.lock CHANGELOG.md
git commit -m "chore(release): vX.Y.Z"
git push origin develop
4. Closing Issue の収集
- 前回タグ〜HEADのコミットからPR番号抽出
LAST_TAG=$(git describe --tags --abbrev=0)
PR_NUMBERS=$(git log ${LAST_TAG}..HEAD --oneline \
| grep -oE '(#[0-9]+)|\bMerge pull request #[0-9]+' \
| grep -oE '[0-9]+' | sort -u)
- 各PR本文から closing keyword 抽出
CLOSING_ISSUES=""
for pr in $PR_NUMBERS; do
BODY=$(gh pr view "$pr" --json body -q '.body' 2>/dev/null || true)
ISSUES=$(echo "$BODY" \
| grep -oiE '(close[sd]?|fix(e[sd])?|resolve[sd]?)\s+#[0-9]+' \
| grep -oE '[0-9]+' || true)
CLOSING_ISSUES="$CLOSING_ISSUES $ISSUES"
done
CLOSING_ISSUES=$(echo "$CLOSING_ISSUES" | tr ' ' '\n' | sort -u | grep -v '^$')
- PR番号を除外してIssueのみ残す
REAL_ISSUES=""
for num in $CLOSING_ISSUES; do
IS_PR=$(gh api "repos/{owner}/{repo}/issues/$num" \
--jq 'has("pull_request") and .pull_request != null' 2>/dev/null || echo "false")
if [ "$IS_PR" = "false" ]; then
REAL_ISSUES="$REAL_ISSUES $num"
fi
done
- PR本文用に出力
for num in $REAL_ISSUES; do
echo "Closes #$num"
done
5. main へマージ
# 推奨: 既存スクリプト経由
./scripts/prepare-release.sh
# または prepare-release workflow を直接起動
gh workflow run prepare-release.yml
# 手動PR作成の場合
gh pr create --base main --head develop \
--title "chore(release): vX.Y.Z"
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.
- 8d ago First seen · 143 lines · 52 tokens per session scan A cd2498036165
release is a skill published in the GitHub repository akiojin/llmlb (10 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 1,057 once invoked, about $0.0002 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-10-21.
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
Fully automate a release with version-bump and childhood.
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.
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.