What is prepare-release?

A skill for preparing a release of the law-scrapper-mcp project, including changelog files, version updates, checks, and a commit. A changelog records notable changes between software releases.

Use it when preparing a versioned release, reviewing commits since the previous tag, classifying changes, and running release checks.

It gives releases a repeatable checklist and keeps version numbers synchronized across the project.

How numikel/law-scrapper-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to numikel/law-scrapper-mcp. 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/numikel/law-scrapper-mcp/main/.claude/skills/prepare-release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/numikel/law-scrapper-mcp

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/skills/numikel/law-scrapper-mcp/prepare-release/github.svg)](https://agentmods.dev/skills/numikel/law-scrapper-mcp/prepare-release)

Your own site

<a href="https://agentmods.dev/skills/numikel/law-scrapper-mcp/prepare-release"><img src="https://agentmods.dev/badge/skills/numikel/law-scrapper-mcp/prepare-release/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/skills/numikel/law-scrapper-mcp/prepare-release"><img src="https://agentmods.dev/badge/skills/numikel/law-scrapper-mcp/prepare-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

Security scan B 1 finding. 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.00052	$0.01306
Opus 5.5	$0.00021	$0.00522
Sonnet 5.5	$0.00010	$0.00261
Haiku 4.5	$0.00005	$0.00131

Measured 6d ago against content hash 440d33601471, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

prepare-release scanned grade B with 1 finding 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.

Asks the agent to reveal its instructionsmediumSystem prompt leakage

Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.

Output instructions for the maintainer to tag and push the release:

.claude/skills/prepare-release/SKILL.md · 126 lines

How it starts

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

Prepare release

Prepare a law-scrapper-mcp release locally. No LLM calls in CI — all changelog generation and version synchronization happen here in the IDE.

Invocation

User runs /prepare-release X.Y.Z (or /prepare-release vX.Y.Z).

Always strip any leading v prefix so that X.Y.Z is pure semver (e.g., 2.5.0).

Mandatory checklist (follow in order)

1. Resolve commit range

Run the git release info script to discover changes since the last tagged release:

uv run python scripts/git_release_info.py --range

If no prior tags exist or if --range reports no commits since the last tag, stop and confirm with the user before proceeding with an empty changelog.

2. Classify commits

Group commit subjects using Conventional Commits into Keep a Changelog categories:

Conventional Commit Type	Keep a Changelog Section
`feat`	`Added`
`fix`	`Fixed`
`perf`, `refactor`	`Changed`
`docs`	`Changed` (omit if purely internal)
`security`	`Security`
`deprecate`	`Deprecated`
`remove`	`Removed`
`ci`, `build`, `chore`	Omit unless user-facing
`BREAKING CHANGE:` / `!`	`Changed` (with explicit breaking change note)

Write user-facing bullet points in English. Avoid raw commit SHAs in bullet text.

3. Write per-version changelog

Create docs/changelogs/vX.Y.Z.md using docs/templates/changelog-version-template.md:

Follow Keep a Changelog 1.1.0 standards.
Include release date in UTC (YYYY-MM-DD).
Include relevant sections (Added, Changed, Deprecated, Removed, Fixed, Security) and omit empty ones.
Refer to docs/changelogs/v2.4.0.md for structure and tone consistency.

4. Update root CHANGELOG.md

Update the root CHANGELOG.md using docs/templates/release-summary-template.md:

Move relevant [Unreleased] items into a new version section ## [X.Y.Z] - YYYY-MM-DD.
Add a summary referencing the per-version file docs/changelogs/vX.Y.Z.md.
Keep the [Unreleased] section header ready for future changes.

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

6d ago Changed · -4 lines 440d33601471
19d ago Changed · +2 lines be94162d1ef1
2mo ago First seen · 128 lines · 52 tokens per session scan B 57fcfde6a74d

Subscribe to this mod's changes

prepare-release is a skill published in the GitHub repository numikel/law-scrapper-mcp (23 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 1,306 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow Releases

prepare-release next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
prepare-releasenumikel/law-scrapper-mcp	Skill	23	yesterday	MIT	B	52	Claude Code
release-announcementpaperclipai/paperclip	Skill	111k	yesterday	MIT	A	42	Claude Code, Codex
releasethedotmack/claude-mem	Skill	114k	yesterday	Apache-2.0	A	13	Claude Code
release-notesphuryn/pm-skills	Skill	28k	8d ago	MIT	A	57	Claude Code
multi-agent-release-managerchromium/chromium	Skill	25k	yesterday	BSD-3-Clause	A	27	Claude Code, Codex
pack-submitaeonfun/aeon	Skill	788	yesterday	MIT	A	27	Claude Code, Codex
updater_guidesiddsachar/row-bot	Skill	1.7k	yesterday	Apache-2.0	A	22	Claude Code, Codex

law-scrapper-mcp: Skill for Claude Code