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/zjshen14/opencli/changelognpx skills add zjshen14/opencli --skill changeloggit clone --depth 1 https://github.com/zjshen14/opencliWrote 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/zjshen14/opencli/changelog)<a href="https://agentmods.dev/skills/zjshen14/opencli/changelog"><img src="https://agentmods.dev/badge/skills/zjshen14/opencli/changelog.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.00033 | $0.00246 |
| Opus 5 | $0.00016 | $0.00123 |
| Sonnet 5 | $0.00007 | $0.00049 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
changelog 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.
What it actually says
Generate a user-facing changelog grouped into Added / Changed / Fixed sections.
Recent git history: !{git log --oneline -30 2>/dev/null || echo "(no git history available)"}
Recent tags: !{git tag --sort=-creatordate 2>/dev/null | head -5 || echo "(no tags)"}
Scope: $ARGUMENTS
Steps:
- If Scope is non-empty (e.g. a git ref range like
v1.2.0..HEADor a target version tag), rungit log --oneline <scope>to get the relevant commits; otherwise use the recent history shown above. - Group commits into Added, Changed, and Fixed — skip merge commits and CI/chore noise.
- Write clean, user-facing bullet points — rephrase commit messages for clarity rather than copying them verbatim.
- Output as Markdown with a version heading if a version was specified.
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 · 24 lines · 33 tokens per session scan A c06047dc1334
changelog is a skill published in the GitHub repository zjshen14/opencli (2 stars, last pushed 11d ago), licensed MIT. It adds 33 tokens to every session and 246 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-31.
Other skills, from other repositories
release-bump-changelog
Use this skill when preparing a release bump or updating release notes. It writes a launch-style release story from the actual change set, then runs cargo bump so the generated GitHub notes and the marketing copy land together in CHANGELOG.md.
release
Dispatch a Chamber release build to either the insiders channel (Azure blob, Windows + macOS, invite-only testers) or the stable channel (public GitHub Releases, Windows + macOS). Use this skill whenever the user asks to release, cut, publish, promote, ship a build, push to insiders, send to testers, go public, or…
akiship
Full release ritual end-to-end — front-loaded checks, then an unattended pass. ACTIVATION IS LITERAL: this skill runs only on a user turn containing the exact token /akiship that asks for the run to be performed. Nothing else activates it — not the bare word "akiship", not a release-flavored paraphrase, and never a…
project-release-check
Validate this example project's release readiness. Use before publishing a release candidate.
vc-update
Pull latest agent harness improvements from the remote kit repository. Shows a dry-run diff summary, waits for confirmation, then applies updates.
vc-publish
Use when publishing harness improvements to the remote kit repo. Diffs managed files, shows what changed, bumps version, and pushes. Counterpart to vc-update (pull).