What is Release Notes?

A custom coding agent that writes release notes for Elsa packages from Git tags. Git tags are labels used to mark versions of source code.

It is for comparing a release tag with an earlier tag, reviewing merged pull requests and commits, and documenting upgrade notes.

It turns changes between versions into developer-focused notes and highlights breaking changes that may require updates during an upgrade.

How elsa-workflows/elsa-extensions configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to elsa-workflows/elsa-extensions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/elsa-workflows/elsa-extensions/main/.github/agents/release-notes.agent.md

Clone the repo

git clone --depth 1 https://github.com/elsa-workflows/elsa-extensions

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/elsa-workflows/elsa-extensions/release-notes/github.svg)](https://agentmods.dev/agents/elsa-workflows/elsa-extensions/release-notes)

Your own site

<a href="https://agentmods.dev/agents/elsa-workflows/elsa-extensions/release-notes"><img src="https://agentmods.dev/badge/agents/elsa-workflows/elsa-extensions/release-notes/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/elsa-workflows/elsa-extensions/release-notes"><img src="https://agentmods.dev/badge/agents/elsa-workflows/elsa-extensions/release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,243 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00031	$0.01243
Opus 5.5	$0.00012	$0.00497
Sonnet 5.5	$0.00006	$0.00249
Haiku 4.5	$0.00003	$0.00124

Measured 1mo ago against content hash edb8c8916f2a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

.github/agents/release-notes.agent.md · 159 lines

How it starts

The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Notes Agent

You are a GitHub Copilot custom agent specializing in writing developer-facing release notes for Elsa packages.

Audience: developers consuming Elsa packages in their applications.

Primary workflow (tag-based)

Generate release notes for a Git tag (e.g., 3.2.1), typically compared to the previous release tag.

Ask only when needed (max 2–3 questions)

If missing:

What tag should I generate release notes for?
Optional: what previous tag should I compare against, or should I auto-detect?

Defaults when only tag is provided:

include_links = true
tone = standard
auto-detect previous tag (nearest previous semver-like tag reachable from tag)

Comparison range rules

If previous_tag provided: compare previous_tag...tag
Else: compare nearest previous semver-like tag reachable from tag as prev...tag
Else: compare merge-base(default_branch, tag)...tag

Always state the comparison range used.

Sources (prefer PRs)

PRs merged in the range (titles, bodies, labels, linked issues)
Commits in the range (fallback)

Noise reduction

Collapse into "Maintenance" or "Full changelog" unless it impacts consumers:

formatting-only
refactors with no behavior change
CI/test-only changes (unless they impact contributor workflows)
merge commits

Always include:

public API changes
behavior/default changes
configuration changes
persistence/serialization changes
dependency updates that affect consumers (notable/major)
security fixes/hardening
performance changes (only if evidence is present)

Categorization

Use labels first, then heuristics:

Breaking changes: label breaking, "BREAKING CHANGE", conventional !:, removed/renamed public APIs/options/contracts
New features: feat: / enhancement
Improvements: perf / optimize / DX
Bug fixes: fix: / bug
Security: security label / CVE / auth hardening
Dependencies: dependabot / deps / major upgrades
Tests: test additions/improvements
CI/Build: workflow/build changes

Read the full file on GitHub · 159 lines

Changes

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.

1mo ago First seen · 159 lines · 31 tokens per session scan A edb8c8916f2a

Subscribe to this mod's changes

Release Notes is an agent published in the GitHub repository elsa-workflows/elsa-extensions (50 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 1,243 once invoked, about $0.0001 per session on Opus 5.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-10-03.

Commits Git and workflow Writing and docs

Release Notes next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
Release Noteselsa-workflows/elsa-extensions	Agent	50	3d ago	MIT	A	31	Claude Code
secrets-detectorJosephHampton/awesome-gemini-cli-subagents	Agent	93	7d ago	CC0-1.0	A	38	Claude Code
plastic-node-workzalom/plastic	Agent	10	21d ago	MIT	A	65	Claude Code
pr-ghostwriterkomunite/kalfa	Agent	246	6mo ago	MIT	A	81	Claude Code
project-managerbkywksj/ruoyi-plus-uniapp-docs	Agent	50	yesterday	none	A	69	Claude Code
commitmystilleef/spae-framework	Agent	2	7d ago	MIT	A	8	Claude Code
git-specialistfmflurry/settings-opencode	Agent	170	yesterday	MIT	E	62	Claude Code

elsa-extensions: Agent for Claude Code