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/jackin-project/jackin-dev/jackin-release-notesnpx skills add jackin-project/jackin-dev --skill jackin-release-notesgit clone --depth 1 https://github.com/jackin-project/jackin-devWrote 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/jackin-project/jackin-dev/jackin-release-notes)<a href="https://agentmods.dev/skills/jackin-project/jackin-dev/jackin-release-notes"><img src="https://agentmods.dev/badge/skills/jackin-project/jackin-dev/jackin-release-notes.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.00044 | $0.00828 |
| Opus 5 | $0.00022 | $0.00414 |
| Sonnet 5 | $0.00009 | $0.00166 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
jackin-release-notes 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 3d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jackin-release-notes
Classify every PR merged since the last release tag into a Keep a Changelog bucket, then write the [Unreleased] section of CHANGELOG.md. The bar is exhaustive — every merged PR accounted for, none dropped, none doubled.
When to use
- Before a release, to populate the changelog.
- When the operator asks to preview what the next release would contain.
When NOT to use
- Cutting the release itself →
jackin-release(it runs this skill as its notes step).
Process
-
Find the boundary.
LAST_TAG=$(git describe --tags --abbrev=0); if none, start from the initial commit (git rev-list --max-parents=0 HEAD).TAG_DATE=$(git log -1 --format=%aI "$LAST_TAG").Done when you hold the boundary commit and its date.
-
Gather merged PRs.
gh pr list --state merged --base main --search "merged:>$TAG_DATE" --json number,title,labels,mergedAt.Done when every PR merged after the tag is in the list.
-
Classify each. Sort by Conventional Commits prefix and label:
Prefix / label Bucket feat:/featureAdded fix:/bugFixed security:Security refactor:,chore:,docs:,ci:,build:Changed deprecate:Deprecated remove:Removed no match Changed (default) Strip the prefix from the title; capitalize the first word (
feat: add TUI launcher→Add TUI launcher).Done when every PR sits in exactly one bucket.
-
Catch ungrouped commits.
git log <last-tag>..HEAD --oneline --no-merges; for each,gh pr list --state merged --search "<sha>". Commits with no PR land under Ungrouped commits.Done when every non-merge commit since the tag is matched to a PR or listed.
-
Write
[Unreleased]. Keep a Changelog format: one section per non-empty bucket, each entry linking its PR ([#N](…/pull/N)). Replace the existing[Unreleased]block (between## [Unreleased]and the next## [) — ask before overwriting entries an operator already edited. Keep the<!-- next-header -->marker intact.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 69 lines · 44 tokens per session scan A 2e76f3efb58e
jackin-release-notes is a skill published in the GitHub repository jackin-project/jackin-dev (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 44 tokens to every session and 828 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
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.
release-notes
Draft concise release notes.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
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…
store-update
在 CCX Desktop 发布后下载 Store MSIX 并生成发布公告。用户提到 Store 上架、MSIX、从 GitHub Release 下载 store.msix、发布后同步 Windows Store、从 release 填写商店更新内容时必须使用此技能。该技能会下载最新 GitHub Release 的 amd64/arm64 MSIX，校验 sha256，从 Release body 生成 Store listing releaseNotes 预览，并输出手动上传指引。.
publish-registry
Publish @agentos-software/ registry packages from AgentOS. Use whenever the user asks to publish or release registry software/agent packages.