Borrowing it
Nothing to install: this file belongs to eddiesanjuan/markupr. 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/eddiesanjuan/markupr/main/.claude/commands/release-check.mdgit clone --depth 1 https://github.com/eddiesanjuan/markuprWrote 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/eddiesanjuan/markupr/release-check)<a href="https://agentmods.dev/commands/eddiesanjuan/markupr/release-check"><img src="https://agentmods.dev/badge/commands/eddiesanjuan/markupr/release-check/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/commands/eddiesanjuan/markupr/release-check"><img src="https://agentmods.dev/badge/commands/eddiesanjuan/markupr/release-check.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.00379 |
| Opus 5.5 | $0.00000 | $0.00152 |
| Sonnet 5.5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
release-check 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 1mo 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.
What it actually says
Pre-Release Checklist
Validate that markupr is ready for a new release. Run this before bumping the version.
Instructions
-
Verify the build succeeds:
npm run buildThis builds the desktop app, CLI, and MCP server. All three must succeed.
-
Run the full test suite:
npm test -- --runAll tests must pass. Do not proceed if any fail.
-
Run lint and type checking:
npm run lint npm run typecheckZero errors required. Warnings are acceptable but should be noted.
-
Check version consistency:
- Read
package.jsonfor the current version - Read
CLAUDE.mdfor the documented version - Read
electron-builder.ymlfor the builder config version - Flag any mismatches
- Read
-
Review recent changes since last release:
git log --oneline $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~20)..HEADCategorize commits as: features, fixes, chores, breaking changes.
-
Check for uncommitted changes:
git statusWorking tree should be clean before release.
-
Verify native dependencies:
npm ls keytar sharp whisper-nodeEnsure native modules are installed and compatible.
-
Produce a release summary:
- Suggested version bump (patch/minor/major) based on changes
- Draft CHANGELOG entry
- Any blockers or risks identified
- Confirmation: "Ready for release" or "Not ready -- [reasons]"
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.
- 1mo ago First seen · 55 lines · 0 tokens per session scan A 0a11e9694b5c
release-check is a command published in the GitHub repository eddiesanjuan/markupr (18 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 379 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-30.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or 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.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
rally-merge-pr
You are merging the current branch's PR and syncing the feature branch with main. Follow each step exactly.