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 FortiumPartners/ensemble --skill changelog-generatorgit clone --depth 1 https://github.com/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/changelog-generator)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/changelog-generator"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/changelog-generator/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/fortiumpartners/ensemble/changelog-generator"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/changelog-generator.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.00000 | $0.00861 |
| Opus 5 | $0.00000 | $0.00430 |
| Sonnet 5 | $0.00000 | $0.00172 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
changelog-generator 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 6d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Generator Skill
Quick Reference - Parse conventional commits and generate categorized changelog
Mission
Generate changelog from conventional commits with categorization (Features, Bug Fixes, Breaking Changes, Performance, Documentation) and formatted output for release notes.
Core Capabilities
- Conventional Commit Parsing: Extract type, scope, description, breaking changes
- Change Categorization: Group by type (feat, fix, perf, docs, refactor, test, chore)
- Breaking Change Detection: Identify BREAKING CHANGE footer and ! syntax
- Semantic Version Integration: Suggest version bump based on change types
- Multi-Format Output: Markdown, JSON, plain text formats
Quick Start
const { ChangelogGenerator } = require('./scripts/generate-changelog.js');
const generator = new ChangelogGenerator({
fromTag: 'v2.0.0',
toTag: 'HEAD',
format: 'markdown'
});
const changelog = await generator.generate();
console.log(changelog);
Conventional Commit Format
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
Supported Types:
feat: New feature → Features sectionfix: Bug fix → Bug Fixes sectionperf: Performance improvement → Performance sectiondocs: Documentation → Documentation sectionstyle: Code style (no logic change)refactor: Code refactoringtest: Test additions/updateschore: Build/tooling changes
Breaking Changes:
BREAKING CHANGE:footer → Breaking Changes section!after type/scope → Breaking Changes section
Category Priority
- Breaking Changes (highest impact)
- Features (new functionality)
- Bug Fixes (fixes)
- Performance (optimizations)
- Documentation (docs updates)
Example Output
## [2.1.0] - 2025-11-05
### Breaking Changes
- **auth**: Remove deprecated OAuth 1.0 support (c4f3b2a)
### Features
- **api**: Add rate limiting with Redis backend (a1b2c3d)
- **ui**: Implement dark mode toggle (e5f6g7h)
### Bug Fixes
- **database**: Fix connection pool exhaustion (i8j9k0l)
- **auth**: Resolve JWT token expiration edge case (m1n2o3p)
### Performance
- **api**: Optimize query performance with database indexes (q4r5s6t)
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.
- 6d ago First seen · 132 lines · 0 tokens per session scan A 965b501fa03e
changelog-generator is a skill published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 861 tokens. 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
cli-git-conventional
Enforce Conventional Commits v1.0.0, SemVer 2.0.0, branch naming, commit guard, full-directory AI marker audits, and human ghostwriter style on all git/jj operations. Zero AI markers. Use on 'commit', 'branch', 'tag', 'release', 'changelog', 'semver', 'bump version', 'next version', 'CHANGELOG.md', 'audit markers'…
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…
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
install
This skill should be used when the user asks to "install pikiclaw", "build and install", "deploy locally", "update local binary", "release", or "publish".
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.
git-workflow
Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…