Borrowing it
Nothing to install: this file belongs to heygen-com/heygen-cli. 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/heygen-com/heygen-cli/main/.agents/skills/changelog-cli/SKILL.mdgit clone --depth 1 https://github.com/heygen-com/heygen-cliWrote 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/heygen-com/heygen-cli/changelog-cli)<a href="https://agentmods.dev/skills/heygen-com/heygen-cli/changelog-cli"><img src="https://agentmods.dev/badge/skills/heygen-com/heygen-cli/changelog-cli/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/heygen-com/heygen-cli/changelog-cli"><img src="https://agentmods.dev/badge/skills/heygen-com/heygen-cli/changelog-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00064 | $0.01061 |
| Opus 5.5 | $0.00026 | $0.00424 |
| Sonnet 5.5 | $0.00013 | $0.00212 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
changelog-cli 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 22d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Generator
Step 7 of the release; the release-cli skill runs it for you. It also works on its own.
Generate release notes for a stable release by summarizing git commits since the last stable tag.
Step 1: Determine the range
# Find the last stable tag
LAST_STABLE=$(git tag --list 'v*' --sort=-v:refname | grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' | head -n 1)
If LAST_STABLE is empty (first stable release), use the full history by
omitting the range:
# If LAST_STABLE is set:
git log "${LAST_STABLE}..origin/main" --oneline
# If LAST_STABLE is empty (first release):
git log origin/main --oneline
If a version argument was provided (e.g. v0.0.6), use it as
the heading. Otherwise, infer the next version by bumping the patch of
$LAST_STABLE (or use v0.1.0 if no stable tag exists).
Step 2: Read the full commit details
Use the same range logic from Step 1 (with or without $LAST_STABLE):
# With a previous stable tag:
git log "${LAST_STABLE}..origin/main" --format="### %h%n%s%n%n%b%n---"
# First release (no stable tag):
git log origin/main --format="### %h%n%s%n%n%b%n---"
Also read the PR descriptions for any merged PRs in the range to get richer context on what changed and why:
# Extract PR numbers from commit messages (works on both GNU and BSD grep)
git log ${LAST_STABLE:+"${LAST_STABLE}.."}origin/main --oneline | grep -o '#[0-9]\+' | tr -d '#' | sort -u
For each PR number, read the PR body:
gh pr view <number> --json title,body --jq '.title + "\n" + .body'
Step 3: Categorize and write the changelog
Group changes into these categories (omit empty categories):
- New - new commands, features, or capabilities
- Improved - enhancements to existing behavior
- Fixed - bug fixes
- Internal - changes with no user-visible effect (CI, refactors, docs)
A codegen resync is not automatically Internal. What it did to the command surface is what a user cares about, so a resync that added a command or a flag is a New entry naming that command or flag, carrying the resync's PR number. List a resync under Internal only when it changed nothing a user can type.
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.
- 22d ago Changed · +2 lines · +18 tokens per session 4e12d07d6c03
- 2mo ago First seen · 119 lines · 46 tokens per session scan A f14f7ab14afe
changelog-cli is a skill published in the GitHub repository heygen-com/heygen-cli (164 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 1,061 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
release
Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.
tools-checkout
Fetch the internal tools repository at a pinned release.
ship
Release pipeline for already-done local work. Dispatches /ground-state pre-flight, runs the project test suite, drafts a commit message, pushes, and opens a PR with a structured verification summary. Use when local changes are ready to hand off to review — e.g. 'ship this', 'push and open a PR', 'release this work'.…
python-format
Formats Python files with ruff format and reports which files changed.
hotfix-branch
Prepares a hotfix on a branch cut from the latest release tag. Use when a production bug needs a patch release.