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.
curl -O https://raw.githubusercontent.com/numikel/law-scrapper-mcp/main/.claude/skills/prepare-release/SKILL.mdgit clone --depth 1 https://github.com/numikel/law-scrapper-mcpWrote 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/skills/numikel/law-scrapper-mcp/prepare-release)<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.
<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>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.01238 |
| Opus 5 | $0.00026 | $0.00619 |
| Sonnet 5 | $0.00010 | $0.00248 |
| Haiku 4.5 | $0.00005 | $0.00124 |
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 10d 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: How it starts
The opening of the file, as written. The whole thing — 128 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
vprefix so thatX.Y.Zis 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.mdfor 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.
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.
- 10d ago First seen · 128 lines · 52 tokens per session scan B 57fcfde6a74d
prepare-release is a skill published in the GitHub repository numikel/law-scrapper-mcp (20 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 1,238 once invoked, about $0.0003 per session on Opus 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.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.