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 commands/berrydev-ai/blockdoc-python/add-to-changeloggit clone --depth 1 https://github.com/berrydev-ai/blockdoc-pythonWhat 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.00000 | $0.00387 |
| Opus 5 | $0.00000 | $0.00193 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
add-to-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.
What it actually says
Update Changelog
This command adds a new entry to the project's CHANGELOG.md file.
Usage
/add-to-changelog <version> <change_type> <message>
Where:
<version>is the version number (e.g., "1.1.0")<change_type>is one of: "added", "changed", "deprecated", "removed", "fixed", "security"<message>is the description of the change
Examples
/add-to-changelog 1.1.0 added "New markdown to BlockDoc conversion feature"
/add-to-changelog 1.0.2 fixed "Bug in HTML renderer causing incorrect output"
Description
This command will:
- Check if a CHANGELOG.md file exists and create one if needed
- Look for an existing section for the specified version
- If found, add the new entry under the appropriate change type section
- If not found, create a new version section with today's date
- Format the entry according to Keep a Changelog conventions
- Commit the changes if requested
The CHANGELOG follows the Keep a Changelog format and Semantic Versioning.
Implementation
The command should:
- Parse the arguments to extract version, change type, and message
- Read the existing CHANGELOG.md file if it exists
- If the file doesn't exist, create a new one with standard header
- Check if the version section already exists
- Add the new entry in the appropriate section
- Write the updated content back to the file
- Suggest committing the changes
Remember to update the package version in __init__.py and setup.py if this is a new version.
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 · 51 lines · 0 tokens per session scan A d918c6233919
add-to-changelog is a command published in the GitHub repository berrydev-ai/blockdoc-python (3 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 387 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-08-31.
Other commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Create a full stable release for the project. Optionally pass a title suffix (e.g., "Template Presets Fix") or extra notes.
SHIP_RELEASE
Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.