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 skills add joaquimscosta/arkhe-claude-plugins --skill generating-changeloggit clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-pluginsWrote 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/joaquimscosta/arkhe-claude-plugins/generating-changelog)<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/generating-changelog"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/generating-changelog/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/joaquimscosta/arkhe-claude-plugins/generating-changelog"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/generating-changelog.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.00117 | $0.01689 |
| Opus 5.5 | $0.00047 | $0.00676 |
| Sonnet 5.5 | $0.00023 | $0.00338 |
| Haiku 4.5 | $0.00012 | $0.00169 |
Grade A, and why
generating-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 yesterday.
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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Changelog Generation
Automatically analyze git commit history and generate comprehensive changelogs following industry-standard formats.
Auto-Invoke Triggers
This skill automatically activates when:
- Editing changelog files:
CHANGELOG.md,CHANGELOG.txt,HISTORY.md - Mentioning keywords: "changelog", "release notes", "version", "semantic versioning"
- Git tagging operations: Creating or discussing version tags
- Release preparation: Discussing release preparation or deployment
What This Skill Delivers
When invoked, this skill provides:
1. Git History Analysis Report
- Commit range analysis (since last tag or specified range)
- Commit categorization by type (feat, fix, docs, etc.)
- Semantic version bump recommendation (MAJOR, MINOR, PATCH)
- Breaking changes detection
- Author and PR number extraction
2. Formatted Changelog
Choose from multiple formats:
- Keep a Changelog (default) - Industry standard, human-friendly
- Conventional - Follows Conventional Commits specification
- GitHub - GitHub-style release notes with PR links
3. Update Strategy
- Append to existing CHANGELOG.md (preserves history)
- Overwrite with fresh changelog
- Create new version section
- Merge with existing sections
Common Use Cases
Project Types
- Microservices: Track changes across multiple services
- Frontend Applications: UI updates and features
- API Development: REST API versioning and breaking changes
- Infrastructure: Deployment, CI/CD, DevOps updates
- Documentation: Technical docs, API docs, guides
Conventional Commit Examples
The skill recognizes standard commit conventions:
feat: add new authentication endpoint
fix: resolve token expiration issue
docs: update API documentation
refactor: optimize database queries
perf: improve calculation performance
test: add integration tests
build: upgrade framework version
ci: configure automated testing
chore: update dependencies
What ships with it
3 files 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.
- yesterday First seen · 217 lines · 117 tokens per session scan A 6d6e1873d849
generating-changelog is a skill published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed yesterday), licensed MIT. It adds 117 tokens to every session and 1,689 once invoked, about $0.0005 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-10-16.
Other skills, from other repositories
dev-finish
Close out a session — summarise what changed, capture what was learned, and prepare the commit.
dev-rc
The last gate before merge — QA, security audit, review and changelog, with objective pass conditions.
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.