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 skills/bravew/trove/trove-release-notesnpx skills add bravew/trove --skill trove-release-notesgit 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/skills/bravew/trove/trove-release-notes)<a href="https://agentmods.dev/skills/bravew/trove/trove-release-notes"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-release-notes.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 | $0.00027 | $0.00366 |
| Opus 5 | $0.00014 | $0.00183 |
| Sonnet 5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
trove-release-notes 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
Trove · v2026.7.4
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
Release Notes Conventions
Format
# Release [version] — [date]
## Highlights
One-paragraph summary of the most impactful changes.
## New Features
- **[Feature Name]** — Brief description of what users can now do
## Improvements
- **[Area]** — What got better and why it matters
## Bug Fixes
- Fixed [issue] where [symptom] occurred when [trigger]
## Breaking Changes
- **[Change]** — What changed, migration steps
## Known Issues
- [Issue] — workaround if available
Writing Guidelines
- Write for users, not developers
- Lead with benefits, not implementation details
- Use active voice ("You can now..." not "Added ability to...")
- Group related changes together
- Include screenshots/GIFs for visual changes
Changelog Updates
When asked to update CHANGELOG.md, derive the version from the repo's
existing versioning policy. For Trove CalVer, use YY.M.DD and append
.patch only when a release for the same date already exists. Insert the new
section directly below the changelog title, include only sections supported by
the actual git history, and commit only when the user explicitly asked for a
commit.
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 · 56 lines · 27 tokens per session scan A c0af0b78eb61
trove-release-notes is a skill published in the GitHub repository bravew/trove (10 stars, last pushed 6d ago), licensed MIT. It adds 27 tokens to every session and 366 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 skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…