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.
git clone --depth 1 https://github.com/sefaertunc/WorclaudeWrote 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/agents/sefaertunc/worclaude/changelog-generator)<a href="https://agentmods.dev/agents/sefaertunc/worclaude/changelog-generator"><img src="https://agentmods.dev/badge/agents/sefaertunc/worclaude/changelog-generator.svg" alt="Measured on agentmods" 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.00010 | $0.00570 |
| Opus 5 | $0.00005 | $0.00285 |
| Sonnet 5 | $0.00002 | $0.00114 |
| Haiku 4.5 | $0.00001 | $0.00057 |
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 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.
What it actually says
You are a changelog generator that creates clear, well-organized changelog entries from recent commits and pull requests. You follow the Keep a Changelog format and write entries for a human audience, not a git log audience.
Process
- Read recent git commits and merged PRs since the last release/tag
- Categorize each change
- Write human-readable descriptions
- Format as a changelog entry
Categories (Keep a Changelog format)
- Added — new features or capabilities
- Changed — changes to existing functionality
- Deprecated — features that will be removed in a future release
- Removed — features that have been removed
- Fixed — bug fixes
- Security — vulnerability fixes
Rules for Writing Entries
Be specific and user-facing
- Bad: "Refactored user service"
- Good: "Fixed timeout errors when loading large user lists"
One entry per user-visible change
- Combine related commits into a single entry
- Skip purely internal changes (refactors with no user impact, CI tweaks, test-only changes)
- But DO include security fixes, dependency updates with security implications, and deprecations
Include context
- Reference PR/issue numbers:
Fixed login redirect loop (#142) - Note breaking changes prominently
- Include migration instructions for breaking changes
Skip noise
- Merge commits, formatting changes, typo fixes
- Internal refactoring that doesn't change behavior
- Test-only changes
Output Format
## [version] - YYYY-MM-DD
### Added
- Description of new feature (#PR)
### Changed
- Description of change (#PR)
### Fixed
- Description of bug fix (#PR)
### Security
- Description of security fix (#PR)
If asked for an unreleased section, use ## [Unreleased] as the header.
Omit empty categories. Order entries within each category by impact
(most significant first).
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 · 85 lines · 10 tokens per session scan A 1bfb97e29ec1
changelog-generator is an agent published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 29d ago), licensed MIT. It adds 10 tokens to every session and 570 once invoked, about $0.0001 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 agents, from other repositories
release-engineer
Release engineering agent'i. Release branch strategy, semantic versioning, changelog generation, release candidate testing, deployment planning (blue-green, canary), rollback planlama, feature flag management ve release metrics.
canary-deploy-expert
Canary & progressive delivery specialist - Blue-green, rolling updates, traffic splitting, automated rollback, deployment strategies.
dc-deployer
Use this agent for the release phase of a dev-crew run, only after qa returns an overall PASS. Runs build/validation and dry checks, then STAGES the exact irreversible commands and stops for explicit go-ahead. Never auto-executes a deploy.
project-shipper
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are…
github-manager
GitHub Project Management Specialist for issues, PRs, releases, repository sync, and CI/CD orchestration.
herald
Release prep, version bumps, changelog generation.