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/edwardangert/docs-agent-plugin/release-notesgit clone --depth 1 https://github.com/EdwardAngert/docs-agent-pluginWhat 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.00012 | $0.00868 |
| Opus 5 | $0.00006 | $0.00434 |
| Sonnet 5 | $0.00002 | $0.00174 |
| Haiku 4.5 | $0.00001 | $0.00087 |
Grade A, and why
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 yesterday.
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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Release Notes
Turn the changes in a release into notes a reader can act on: what changed, why it matters, and what they must do about it.
The argument ($ARGUMENTS) can be a git range (v0.8.0..HEAD), a tag, or the version being released. If omitted, use the range from the last tag to HEAD, and confirm it before writing.
Release notes are a reference content type (see ${CLAUDE_PLUGIN_ROOT}/skills/docs-assist/reference/content-types.md), but they are written for readers deciding whether and how to upgrade, not for maintainers reading history. Commit messages are the input, never the output.
Process
1. Resolve the Range and the Convention
- Resolve
$ARGUMENTSto a concrete range and confirm it. - Find where this project publishes release notes: a
CHANGELOG.md(note its format, such as Keep a Changelog or a summary-first layout), adocs/releases/directory, or GitHub releases (gh release list). Match the existing convention. - Starting fresh with no convention? Offer the
release-notestemplate from the catalog (see${CLAUDE_PLUGIN_ROOT}/skills/docs-assist/reference/templates.md), or default to a summary-first entry: a short plain-language summary of what changed and why, with itemized changes below it.
2. Read the Changes
Gather what actually shipped: git log for the range, merged PR titles and bodies (gh pr list --state merged) when the repo uses them, and the diff for anything ambiguous.
Extract only what a reader can observe:
- New features and capabilities.
- Behavior changes, and especially breaking changes and deprecations.
- Fixes a user would have hit.
- Upgrade steps: migrations, config changes, new requirements.
Drop internal churn (refactors, CI, test-only changes) unless it changes something observable, like performance.
3. Ask for the Why
The diff says what changed; the contributor knows why it matters. One short dig, not a form: what should users notice first, what prompted the headline changes, and is there anything readers must do before or after upgrading? Fold their answer into the summary.
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.
- yesterday First seen · 59 lines · 12 tokens per session scan A 0dc0b2abbedf
release-notes is a command published in the GitHub repository EdwardAngert/docs-agent-plugin (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 868 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.