Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ValorVie/custom-skillsnpx agentmods add skills/valorvie/custom-skills/changelog-guideWrote 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/valorvie/custom-skills/changelog-guide)<a href="https://agentmods.dev/skills/valorvie/custom-skills/changelog-guide"><img src="https://agentmods.dev/badge/skills/valorvie/custom-skills/changelog-guide/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/valorvie/custom-skills/changelog-guide"><img src="https://agentmods.dev/badge/skills/valorvie/custom-skills/changelog-guide.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.00059 | $0.01602 |
| Opus 5 | $0.00030 | $0.00801 |
| Sonnet 5 | $0.00012 | $0.00320 |
| Haiku 4.5 | $0.00006 | $0.00160 |
Grade A, and why
changelog-guide 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Guide
Language: English | 繁體中文
Version: 1.0.0 Last Updated: 2025-12-30 Applicability: Claude Code Skills
Core Standard: This skill implements Changelog Standards. For comprehensive methodology documentation, refer to the core standard.
Purpose
This skill helps write and maintain CHANGELOG.md files following the Keep a Changelog format, ensuring clear communication of changes to users.
Quick Reference
File Structure
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/),
and this project adheres to [Semantic Versioning](https://semver.org/).
## [Unreleased]
## [1.2.0] - 2025-12-15
### Added
- Feature description
### Changed
- Change description
### Fixed
- Bug fix description
[Unreleased]: https://github.com/user/repo/compare/v1.2.0...HEAD
[1.2.0]: https://github.com/user/repo/compare/v1.1.0...v1.2.0
Change Categories
| Category | When to Use | Example |
|---|---|---|
| Added | New features | Add dark mode support |
| Changed | Modifications to existing features | Improve search performance by 50% |
| Deprecated | Features to be removed | Deprecate legacyParse() |
| Removed | Removed features | Remove Node.js 14 support |
| Fixed | Bug fixes | Fix login timeout issue |
| Security | Security patches | Fix XSS vulnerability |
Commit Type to Changelog Mapping
| Commit Type | Changelog Category | Notes |
|---|---|---|
feat |
Added | New features |
fix |
Fixed | Bug fixes |
perf |
Changed | Performance improvements |
security |
Security | Security patches |
BREAKING CHANGE |
Changed or Removed | With BREAKING prefix |
refactor, docs, style, test, chore |
(usually omit) | No user impact |
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 · 236 lines · 59 tokens per session scan A afaafb8d049f
changelog-guide is a skill published in the GitHub repository ValorVie/custom-skills (5 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 1,602 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
team-release
Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.
changelog-automation
Git history'den otomatik changelog, semantic versioning, release notes, conventional commits.
contributing
Codex adapter for the opencode-swarm contribution checklist. Use when preparing user-visible changes, release note fragments, local validation, branch hygiene, PR checklist items, or contribution-policy compliance before publishing work.