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/rossumai/rossum-agents/ds-release-notesgit clone --depth 1 https://github.com/rossumai/rossum-agentsWrote 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/rossumai/rossum-agents/ds-release-notes)<a href="https://agentmods.dev/commands/rossumai/rossum-agents/ds-release-notes"><img src="https://agentmods.dev/badge/commands/rossumai/rossum-agents/ds-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.1 | $0.00000 | $0.00932 |
| Opus 5 | $0.00000 | $0.00466 |
| Sonnet 5 | $0.00000 | $0.00186 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
ds-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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Release Notes
Goal: Generate GitHub release notes for $ARGUMENTS based on changelog and commit history.
Valid Packages
| Package | Changelog | Tag Pattern | Title Format |
|---|---|---|---|
| rossum-mcp | rossum-mcp/CHANGELOG.md |
rossum-mcp-vX.Y.Z |
Rossum MCP X.Y.Z |
| rossum-agent | rossum-agent/CHANGELOG.md |
rossum-agent-vX.Y.Z |
Rossum Agent X.Y.Z |
| rossum-agent-client | rossum-agent-client/CHANGELOG.md |
rossum-agent-client-vX.Y.Z |
Rossum Agent Client X.Y.Z |
| rossum-agent-client-ts | no changelog — use git log | rossum-agent-client-ts-vX.Y.Z |
Rossum Agent Client TS X.Y.Z |
| rossum-agent-tui | no changelog — use git log | rossum-agent-tui-vX.Y.Z |
Fabry X.Y.Z |
Approach
| Step | Action |
|---|---|
| Parse input | Extract package name and version from $ARGUMENTS |
| Validate | Confirm tag exists on GitHub |
| Read changelog | Get release content from CHANGELOG.md (or git log for TUI) |
| Check existing | Verify release notes are empty or confirm overwrite |
| Generate notes | Create markdown following style guide below |
| Update release | Push notes and title to GitHub |
Style Guide
| Release Type | Style |
|---|---|
| Major (X.0.0) | Header with emoji (# Rossum MCP X.0.0), intro sentence, sections with emoji headers |
| Minor (X.Y.0) | Section headers with emoji (## New Tools, ## Improvements, ## Bug Fixes) |
| Patch (X.Y.Z) | Simple section (## Bug Fix or ## Changes) |
| RC (X.Y.ZrcN) | ## Changes since rcN-1 with bullet points (or full changelog for rc0) |
Section Headers
| Section | Header |
|---|---|
| New features | ## New Tools or ## New Features |
| Improvements | ## Improvements or ## Changes |
| Bug fixes | ## Bug Fixes or ## Bug Fix |
| Breaking | ## Breaking Changes |
rossum-agent-tui (Fabry)
No CHANGELOG.md — generate release notes from git history:
| Step | Action |
|---|---|
| Find previous tag | git tag --list 'rossum-agent-tui-v*' --sort=-v:refname |
| Get commits | git log --oneline prev-tag..current-tag -- rossum-agent-tui/ |
Check .agents/ |
Look for release-notes-*.md files with draft content for the version |
| Write notes | Group changes into sections, use commit messages and PR context |
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.
- 6d ago First seen · 94 lines · 0 tokens per session scan A 5a5cd7c5c99c
ds-release-notes is a command published in the GitHub repository rossumai/rossum-agents (11 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 932 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-30.
Other commands, from other repositories
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release
Create a release branch, run changeset version, review changelog, and prepare PR.
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.
release
Walk the llmwiki release process step by step.
ship
Ship is the operational release-prep flow for a connected project repo.