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 viknesh20-20/claude-code-tool-kit --skill changeloggit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kitWrote 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/viknesh20-20/claude-code-tool-kit/changelog)<a href="https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/changelog"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/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/viknesh20-20/claude-code-tool-kit/changelog"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/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.00045 | $0.00691 |
| Opus 5.5 | $0.00018 | $0.00276 |
| Sonnet 5.5 | $0.00009 | $0.00138 |
| Haiku 4.5 | $0.00005 | $0.00069 |
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 1mo 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Changelog
Git History
!git log --oneline --no-merges -50 2>/dev/null
Tags
!git tag --sort=-v:refname 2>/dev/null | head -10
Latest Tag
!git describe --tags --abbrev=0 2>/dev/null || echo "No tags found"
Instructions
Step 1: Determine Range
- If a tag/ref is provided, use:
git log <tag>..HEAD - If "last-release" is specified, find the most recent tag
- If "unreleased" or no argument, show all commits since last tag
Step 2: Gather Commits
Run: git log <range> --oneline --no-merges
For each commit, extract:
- Commit hash (short)
- Commit message
- Author
- Date
- PR number (if referenced)
Step 3: Categorize
Group commits using Keep a Changelog categories:
- Added: New features, endpoints, commands, pages
- Changed: Modifications to existing functionality, API changes
- Fixed: Bug fixes, error corrections
- Deprecated: Features marked for removal
- Removed: Deleted features, removed dependencies
- Security: Vulnerability fixes, security improvements
- Breaking Changes: Changes that require consumer updates
Detection heuristics:
feat:/feature:/add:→ Addedfix:/bugfix:/hotfix:→ Fixedrefactor:/update:/change:→ Changedremove:/delete:/drop:→ Removedsecurity:/vuln:/cve:→ SecurityBREAKING:/BREAKING CHANGE:→ Breaking Changes- Other: categorize by reading the commit message
Step 4: Format Output
# Changelog
## [Unreleased] — YYYY-MM-DD
### Added
- Description of new feature (#PR)
### Changed
- Description of change (#PR)
### Fixed
- Description of fix (#PR)
### Removed
- Description of removal (#PR)
### Security
- Description of security fix (#PR)
### Breaking Changes
- Description of breaking change (#PR)
Step 5: Save or Display
- If a CHANGELOG.md exists, prepend the new section
- If not, create a new CHANGELOG.md
- Always show the generated content for review before saving
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.
- 1mo ago First seen · 97 lines · 45 tokens per session scan A 0675b2eb50a9
changelog is a skill published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 691 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-credit-harvest
Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.
github
Skill "github" from Hmbown/Codewhale, covering github, when to use, setup, workflow and non-goals.
release
Skill "release" from Hmbown/Codewhale, covering release, invocation, non-goals and workflow.
deploy-steward
Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.