Borrowing it
Nothing to install: this file belongs to Tatsh/wiswa-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/Tatsh/wiswa-mcp/master/.claude/skills/make-release/SKILL.mdgit clone --depth 1 https://github.com/Tatsh/wiswa-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/tatsh/wiswa-mcp/make-release)<a href="https://agentmods.dev/skills/tatsh/wiswa-mcp/make-release"><img src="https://agentmods.dev/badge/skills/tatsh/wiswa-mcp/make-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/tatsh/wiswa-mcp/make-release"><img src="https://agentmods.dev/badge/skills/tatsh/wiswa-mcp/make-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.00000 | $0.02713 |
| Opus 5 | $0.00000 | $0.01357 |
| Sonnet 5 | $0.00000 | $0.00543 |
| Haiku 4.5 | $0.00000 | $0.00271 |
Grade A, and why
make-release 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Prepare and publish a new release for the wiswa-mcp project.
You manage the release process: update the changelog, determine the version bump, run pre-commit checks, bump the version, and push, and align GitHub release notes with the changelog.
Workflow
-
Review changes since last tag. Run
git log $(git describe --tags --abbrev=0)..HEAD --onelineto see all commits since the last release. -
Update CHANGELOG.md. Add entries under
[Unreleased]if not already present. Use the appropriate sections: Added, Changed, Fixed, Removed. -
Determine the version bump based on Semantic Versioning:
- patch: bug fixes, dependency updates, documentation changes.
- minor: new features, new commands, new public API additions.
- major: breaking changes to public API, removed commands/functions.
-
Create a new version header below
[Unreleased], moving the unreleased content under it. Format:## [X.Y.Z] - YYYY-MM-DD. Leave[Unreleased]empty above it. -
Launch agents in parallel before bumping:
- copy-editor - to fix prose in the changelog entries.
- qa-fixer - to format and fix any lint/spelling issues.
-
Sync repo state back to
.wiswa.jsonnet. Run the wiswa-sync agent so every hand edit to a Wiswa-managed file since the last regen is reflected in.wiswa.jsonnet. Any release-time discoveries (for example aversion_filesentry that was missing) must round-trip so the next regen reproduces them. -
Run
pre-commit run -aoutside the sandbox to ensure all hooks pass. The hooks write across the worktree, which the sandbox's read-only mount blocks. Fix any issues before proceeding. -
Record the current HEAD before bumping:
git rev-parse HEAD(save this asPRE_BUMP_REF). -
Pre-scan
version_filesfor collision risk. Note OLD (the current[tool.commitizen].version) and NEW (the post-bump version for the selected increment). For each entry in[tool.commitizen].version_files, runrg --fixed-strings --line-number 'OLD' <file>(orgrep -nF 'OLD' <file>). Exactly one match is the canonical version field cz is meant to bump. Every other match is a collision candidate: cz uses plain string substitution, so any substringOLDin the file is replaced withNEW, regardless of context. Save the candidate list (file, line number, full pre-bump line) so the matches can be reverted after the bump. The classic example: OLD0.0.0and NEW0.0.1rewrite a"some-dep": "10.0.0"line into"some-dep": "10.0.1"even though10.0.0is unrelated to the project version.
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.
- 8d ago First seen · 163 lines · 0 tokens per session scan A 6d5304feb175
make-release is a skill published in the GitHub repository Tatsh/wiswa-mcp (0 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,713 tokens. 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 skills, from other repositories
write-release-notes
Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes…
release
Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.
releasing
Use before any release work: the trunk release model, the unstable edge channel, the prepare/release/promotion machinery, release-notes pages, the pre-release artifact smoke test, and, when the plugin channel is enabled, the Claude Code plugin channel.
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.
github-pr-description
Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it…