lazyazure: Skill for Claude Code

.agents/skills/release-summary/SKILL.md

release-summary is a skill for Claude Code, Codex from matsest/lazyazure. It costs 9 tokens per session (827 once invoked), scanned A, original, MIT.

A guide for writing a user-friendly release summary from a project's version history. A release is a published version of software, and a changelog is its list of notable changes.

In plain words
What is it for?
Use it with a release version to find the previous version, review the commits between them, and summarize features, fixes, refactors, and maintenance work.
Why use it?
It turns technical commit messages into a concise explanation of what changed between two versions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is matsest/lazyazure's own configuration. It tells Claude Code and Codex how to work on lazyazure itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything lazyazure configures →

Reuse

Borrowing it

Nothing to install: this file belongs to matsest/lazyazure. 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/matsest/lazyazure/main/.agents/skills/release-summary/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/matsest/lazyazure

Made for: Claude Code, Codex.

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.

agentmods badge for release-summary

README.md
[![agentmods](https://agentmods.dev/badge/skills/matsest/lazyazure/release-summary/github.svg)](https://agentmods.dev/skills/matsest/lazyazure/release-summary)
Your own site
<a href="https://agentmods.dev/skills/matsest/lazyazure/release-summary"><img src="https://agentmods.dev/badge/skills/matsest/lazyazure/release-summary/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.

agentmods 80×15 button for release-summary

Your own site · 80×15
<a href="https://agentmods.dev/skills/matsest/lazyazure/release-summary"><img src="https://agentmods.dev/badge/skills/matsest/lazyazure/release-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 827 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.00827
Opus 5 $0.00005 $0.00413
Sonnet 5 $0.00002 $0.00165
Haiku 4.5 $0.00001 $0.00083

Measured 9d ago against content hash 55865050fc9b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

release-summary 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 9d 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.

.agents/skills/release-summary/SKILL.md · 116 lines

How it starts

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

Release Summary Skill

Description

Generate a user-friendly release summary for the LazyAzure project that complements the auto-generated changelog from GoReleaser.

Usage

The user will specify a release version (e.g., "v0.2.5" or "0.2.5"). You should:

  1. Identify the previous version tag
  2. Get all commits between the previous version and the specified version
  3. Generate a concise, user-facing summary formatted as copyable markdown

Steps

1. Get Version Information

git tag --list --sort=-version:refname | grep -E "^v?[0-9]\+\.[0-9]\+\.[0-9]\+$" | head -20

Find the specified version and the version immediately before it in the sorted list.

2. Get Commits Between Versions

git log --oneline <previous-tag>..<current-tag>

3. Analyze Conventional Commits

Parse the commits and categorize them:

Commit Types:

  • feat: or feat(scope): → New features
  • fix: or fix(scope): → Bug fixes
  • docs: → Documentation (usually filtered out by goreleaser)
  • test: → Tests (usually filtered out by goreleaser)
  • refactor: → Code refactoring
  • chore: → Maintenance tasks
  • perf: → Performance improvements

4. Generate Summary Format

Create a concise summary with these sections:

## What's New in vX.Y.Z

[Brief 1-2 sentence overview of the main changes]

### ✨ Highlights
- Key feature 1 (if any)
- Key feature 2 (if any)
- Notable bug fix or improvement

### 🐛 Bug Fixes
- Brief description of bug fix (user impact focused)

5. Guidelines for Writing

DO:

  • Focus on user impact, not implementation details
  • Use active voice and present tense
  • Be concise (bullet points, not paragraphs)
  • Mention specific features/benefits users will notice
  • Include examples if helpful (e.g., "New keyboard shortcut X to do Y")

DON'T:

  • Include internal refactoring or test changes
  • Mention file names or internal code structure
  • Use technical jargon without explanation
  • Include every single commit (focus on important ones)

Read the full file on GitHub · 116 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.

  1. 9d ago First seen · 116 lines · 9 tokens per session scan A 55865050fc9b

Subscribe to this mod's changes

release-summary is a skill published in the GitHub repository matsest/lazyazure (46 stars, last pushed 7d ago), licensed MIT. It adds 9 tokens to every session and 827 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-30.