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/sp-daewoon/chronicle/releasenpx skills add sp-daewoon/chronicle --skill releasegit clone --depth 1 https://github.com/sp-daewoon/chronicleWhat 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.00075 | $0.00521 |
| Opus 5 | $0.00037 | $0.00260 |
| Sonnet 5 | $0.00015 | $0.00104 |
| Haiku 4.5 | $0.00007 | $0.00052 |
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.
What it actually says
Release Workflow
Cut a release end to end.
1. Promote the changelog
node "${CLAUDE_PLUGIN_ROOT}/scripts/changelog-parse.mjs" release --version <X.Y.Z> --date <today>
2. Gather context for notes
Find the previous tag and the commits/ADRs since then:
PREV=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
COMMITS=$( [ -n "$PREV" ] && git log "$PREV"..HEAD --pretty=format:'%s' || git log --pretty=format:'%s' )
Collect new ADRs by diffing the ADR directory since $PREV (use git diff --name-only --diff-filter=A "$PREV"..HEAD -- <adr.dir>). Build a JSON object { "adrs": [{number,title,file}], "commits": ["..."] }.
3. Synthesize notes
Pipe the JSON into the helper:
echo "$JSON" | node "${CLAUDE_PLUGIN_ROOT}/scripts/release-notes.mjs" --version <X.Y.Z>
This writes RELEASE_NOTES.md and prints the notes. The notes combine the changelog section for this version, new ADRs, and a collapsed commit list.
4. Tag and publish
git tag <tagPrefix><X.Y.Z> # tagPrefix from config, default "v"
If gh is installed and a remote exists, publish:
gh release create <tagPrefix><X.Y.Z> --notes-file RELEASE_NOTES.md
If gh is unavailable, stop here and tell the user the notes are in RELEASE_NOTES.md for manual upload.
Rules
- Never tag before the changelog is promoted (step 1 must precede step 4).
ghis optional — degrade gracefully to the notes file.- Use the real version and date; confirm the version bump with the user if ambiguous.
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 · 57 lines · 75 tokens per session scan A 5ceb92462f11
release is a skill published in the GitHub repository sp-daewoon/chronicle (4 stars, last pushed 3mo ago), licensed MIT. It adds 75 tokens to every session and 521 once invoked, about $0.0004 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 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 Notes Generator
Generate professional software release notes from a commit log: classify changes, write user-facing summaries, draft a publishable announcement, and assess release readiness. Use for release, changelog, version, and deploy requests.
release-notes
基于 git 历史 + issue 引用生成符合 Keep-a-Changelog 规范的发版说明.
wrapup-sprint
Complete a sprint with retrospective, changelog update, release tagging, and (for ships-artifacts projects) release provenance — SBOM, SLSA, and signing. Use when sprint work is done, at the end of a sprint cycle, or before starting a new sprint.
release
Guide the Backend.AI release process - run release.sh, generate changelog via towncrier, consolidate RC entries for final releases with subsection grouping.
submit
Complete submission workflow - quality checks, commit, PR creation, changelog generation, and final push. Use after finishing implementation work.