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/bravew/troveWrote 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/commands/bravew/trove/changelog)<a href="https://agentmods.dev/commands/bravew/trove/changelog"><img src="https://agentmods.dev/badge/commands/bravew/trove/changelog.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.00008 | $0.00378 |
| Opus 5 | $0.00004 | $0.00189 |
| Sonnet 5 | $0.00002 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
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 7d 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
Generate Changelog
You are updating the changelog for a new release.
Versioning Scheme
This project uses Calendar Versioning (CalVer) with the format: YY.M.DD[.patch]
YY- Two-digit year (e.g., 26 for 2026)M- Month without leading zero (1-12)DD- Day of month with leading zero (01-31).patch- Optional patch number for multiple releases on the same day (starts at 1)
Examples:
26.1.29- First release on January 29, 202626.1.29.1- Second release on January 29, 202626.2.1- First release on February 1, 2026
Instructions
- Determine the new version based on today's date
- Check if a release already exists for today — if so, increment the patch number
- Update CHANGELOG.md to add a new section for the new version at the top of the file, right after the '# Changelog' heading and before any existing version sections
Review the recent commits and merged pull requests since the last release to generate meaningful changelog content. Follow the existing format in CHANGELOG.md with sections like:
- Breaking Changes (if any)
- New Features
- Bug Fixes
- Documentation
- Internal/Other changes
Include only the sections that are relevant based on the actual changes. Write clear, user-focused descriptions.
After updating CHANGELOG.md, commit the changes with: docs: update changelog for v{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.
- 7d ago First seen · 45 lines · 8 tokens per session scan A c6c137491050
changelog is a command published in the GitHub repository bravew/trove (10 stars, last pushed 8d ago), licensed MIT. It adds 8 tokens to every session and 378 once invoked, about $0.0000 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 commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.