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/justfinethanku/cc-changelog-plugin/commitnpx skills add justfinethanku/cc-changelog-plugin --skill commitgit clone --depth 1 https://github.com/justfinethanku/cc-changelog-pluginWhat 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.00040 | $0.02413 |
| Opus 5 | $0.00020 | $0.01207 |
| Sonnet 5 | $0.00008 | $0.00483 |
| Haiku 4.5 | $0.00004 | $0.00241 |
Grade A, and why
Git Commit with Auto-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 2d 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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit with Auto-Changelog Skill
Automatically documents code changes in a searchable changelog when committing to git.
Purpose
Every commit creates a structured changelog entry that captures:
- What changed (files, features, fixes)
- Why (decision rationale)
- Issues encountered
- Dependencies added
- Testing notes
- Next steps
All entries are indexed in an auto-generated README for easy searching.
Usage
The skill activates automatically when you ask to commit changes:
"Commit these changes"
"Let's commit this work"
"Create a git commit with changelog for this session"
You can optionally provide a summary:
"Commit with message: Implement sectional evaluation system"
What This Skill Does
1. First-Time Setup (if changelog/ doesn't exist)
- Creates
changelog/directory - Creates
.changelog-keywords.txtwith default tags - Creates initial
README.mdindex - Logs the setup as first changelog entry
2. Every Commit
- Analyzes git changes (
git diff --stat) - Suggests keywords based on file paths
- Prompts for changelog details (what, why, issues)
- Generates timestamped markdown entry
- Regenerates README index
- Stages all changes (code + changelog)
- Creates commit with descriptive message
- Optionally pushes to remote
3. Maintains Searchability
- Auto-updates README with one-line summaries
- Groups entries by month
- Creates keyword index at bottom
- Enables Cmd+F searching across all sessions
Process Flow
-
Check for changes
- Run
git status - If no changes, exit with message
- If changes exist, proceed
- Run
-
First-time setup check
- Look for
changelog/directory - If missing, create full structure
- Add setup entry to changelog
- Look for
-
Analyze changes
- Run
git diff --statfor file summary - Parse file paths to suggest keywords
- Count lines added/removed
- Run
-
Prompt user for details
- Session description (or use provided message)
- Why these changes were made
- Issues encountered (optional)
- Keywords (show suggestions, allow editing)
- Dependencies added (if package.json changed)
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.
- 2d ago First seen · 347 lines · 40 tokens per session scan A 85467cafc6c5
Git Commit with Auto-Changelog is a skill published in the GitHub repository justfinethanku/cc-changelog-plugin (4 stars, last pushed 10mo ago), licensed MIT. It adds 40 tokens to every session and 2,413 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…