Borrowing it
Nothing to install: this file belongs to yorifuji/mcp-wtit. 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/yorifuji/mcp-wtit/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/yorifuji/mcp-wtitWrote 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/commands/yorifuji/mcp-wtit/release)<a href="https://agentmods.dev/commands/yorifuji/mcp-wtit/release"><img src="https://agentmods.dev/badge/commands/yorifuji/mcp-wtit/release.svg" alt="Measured on agentmods" 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.00625 |
| Opus 5 | $0.00000 | $0.00313 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
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 5d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Command
This command automates the release process for mcp-wtit.
Usage
Use this command with a version type: patch, minor, or major
Example: /release patch
Steps
- Run pre-release checks
# Run linting
npm run lint
# Run type checking
npm run typecheck
# Run tests
npm test
# Check coverage
npm run test:coverage
# Build the project
npm run build
# If any checks fail, stop and ask user if they want to continue
- Update version
# Update version based on the argument (patch/minor/major)
# This will create a commit with message "Release x.y.z"
npm version {{VERSION_TYPE}} -m "Release %s"
- Push changes
# Show commits that will be pushed
echo "=== Commits to be pushed ==="
git log origin/main..HEAD --oneline
# Show diff of changes
echo -e "\n=== Changes to be pushed ==="
git diff origin/main..HEAD
# ⚠️ CONFIRM: Ask user "Ready to push these changes to GitHub? (yes/no)" and proceed only if they confirm
# Push the version commit
git push
# Push the version tag
git push origin v$(node -p "require('./package.json').version")
- Create GitHub Release
# Get the new version
VERSION=$(node -p "require('./package.json').version")
# Create release notes based on recent commits
NOTES=$(git log --pretty=format:"- %s" v${VERSION}^..v${VERSION})
# Show release preview
echo "Will create GitHub release v${VERSION} with notes:"
echo "### Changes"
echo "${NOTES}"
# ⚠️ CONFIRM: Ask user "Ready to create GitHub release? (yes/no)" and proceed only if they confirm
# Create GitHub release
gh release create v${VERSION} \
--title "v${VERSION}" \
--notes "### Changes
${NOTES}"
- Publish to npm
# Show package details
npm pack --dry-run
# ⚠️ CONFIRM: Ask user "Ready to publish to npm? (yes/no)" and proceed only if they confirm
# Publish the package
npm publish
- Verify release
# Check npm package
echo "Package published: https://www.npmjs.com/package/mcp-wtit"
# Check GitHub release
echo "GitHub release: https://github.com/yorifuji/mcp-wtit/releases/tag/v$(node -p "require('./package.json').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.
- 5d ago First seen · 102 lines · 0 tokens per session scan A 2cdf7f87910b
release is a command published in the GitHub repository yorifuji/mcp-wtit (0 stars, last pushed 12mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 625 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-09-01.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
Command "release-plan" from alisunstar/OpenSunstar, covering /rd:release-plan — 发布计划, 先读, 执行, 产物 and 人工确认.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.