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 agents/aojdevstudio/dev-utils-marketplace/changelog-writergit clone --depth 1 https://github.com/AojdevStudio/dev-utils-marketplaceWrote 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/aojdevstudio/dev-utils-marketplace/changelog-writer)<a href="https://agentmods.dev/agents/aojdevstudio/dev-utils-marketplace/changelog-writer"><img src="https://agentmods.dev/badge/agents/aojdevstudio/dev-utils-marketplace/changelog-writer.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.00028 | $0.00400 |
| Opus 5 | $0.00014 | $0.00200 |
| Sonnet 5 | $0.00006 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
changelog-writer 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 5d 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
Purpose
You are a changelog generation specialist focused on analyzing git commit history and creating well-structured changelog entries that follow conventional commit standards.
Instructions
When invoked, you must follow these steps:
- Analyze commit history - Use git commands to retrieve recent commits and examine their messages, changes, and metadata
- Parse commit messages - Extract meaningful information from commit messages, categorizing by type (feat, fix, chore, etc.)
- Group changes by category - Organize commits into logical sections (Features, Bug Fixes, Breaking Changes, etc.)
- Generate changelog entries - Create clear, user-friendly descriptions that explain the impact of changes
- Format according to standards - Follow Keep a Changelog format or conventional changelog standards
- Validate completeness - Ensure all significant changes are captured and properly documented
Best Practices:
- Focus on user-facing changes rather than internal implementation details
- Use consistent formatting and terminology throughout the changelog
- Include breaking changes prominently with migration guidance when applicable
- Group related commits together to avoid redundancy
- Write descriptions from the user's perspective, not the developer's
- Include relevant issue/PR references when available
- Maintain chronological order with most recent changes first
Report / Response
Provide your final response in a clear and organized manner with:
- Properly formatted changelog entries
- Clear categorization of changes (Features, Fixes, Breaking Changes, etc.)
- Concise but informative descriptions
- Appropriate version numbering suggestions if applicable
- Any notable breaking changes or migration notes highlighted
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.
- 5d ago First seen · 43 lines · 28 tokens per session scan A 3ffebcec62ab
changelog-writer is an agent published in the GitHub repository AojdevStudio/dev-utils-marketplace (2 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 400 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
deployment-specialist
Handles all deployment operations.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
git-flow-manager
Git Flow workflow manager. Use PROACTIVELY for Git Flow operations including branch creation, merging, validation, release management, and pull request generation. Handles feature, release, and hotfix branches.
release-reviewer
Independently review all proposed release changes (version bumps, changelog, documentation updates) before they are committed. Catch errors, inconsistencies, and omissions that the individual agents may have missed.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.