agentmods.dev

prepare-release

prepare-release is a command for Claude Code from saeedkolivand/ai-job-hunter-app. It costs 20 tokens per session (450 once invoked), scanned A, original, Apache-2.0.

A command for checking whether a project is ready to release by reviewing commits, version consistency, the changelog, and the updater.

In plain words
What is it for?
Use it before publishing a new version of a project.
Why use it?
It helps catch unfinished release work and mismatched version or update information before shipping.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents.

not rated 54repo today A scan 20 tokens original Apache-2.0

Good fit Use it before publishing a new version of a project.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/saeedkolivand/ai-job-hunter-app/prepare-release
View source ↗ saeedkolivand/ai-job-hunter-app aijobhunter.app
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/saeedkolivand/ai-job-hunter-app

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.

agentmods badge for prepare-release

README.md
[![agentmods](https://agentmods.dev/badge/commands/saeedkolivand/ai-job-hunter-app/prepare-release/github.svg)](https://agentmods.dev/commands/saeedkolivand/ai-job-hunter-app/prepare-release)
Your own site
<a href="https://agentmods.dev/commands/saeedkolivand/ai-job-hunter-app/prepare-release"><img src="https://agentmods.dev/badge/commands/saeedkolivand/ai-job-hunter-app/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.

agentmods 80×15 button for prepare-release

Your own site · 80×15
<a href="https://agentmods.dev/commands/saeedkolivand/ai-job-hunter-app/prepare-release"><img src="https://agentmods.dev/badge/commands/saeedkolivand/ai-job-hunter-app/prepare-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 450 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00450
Opus 5 $0.00010 $0.00225
Sonnet 5 $0.00004 $0.00090
Haiku 4.5 $0.00002 $0.00045

Measured 11d ago against content hash 4f912622bb3f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

prepare-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 11d 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.

.claude/commands/prepare-release.md · 20 lines

What it actually says

Prepare release: $ARGUMENTS

  1. Load deployment-rules + token-efficiency.
  2. Bug-catch pre-flight over the release range (git diff <last-release-tag>..HEAD) — no new engine, reuse existing pieces; HIGH/CRITICAL block the release, route each fix to the owning author → re-audit:
    • Green gate — pnpm typecheck + pnpm test + cargo clippy/cargo test (apps/desktop/src-tauri) all pass.
    • Bug-focused critic pass — spawn the touched-domain critics over the range diff with a correctness/bug lens (not just the arch rubric).
    • Impact sanity — codegraph impact <changed-symbol> for changed public symbols → flag callers not updated in the range.
    • Over-engineering — ponytail:ponytail-review over the range.
    • Correctness — the built-in /code-review (code-review ultra is a user-triggered option for high-stakes releases).
  3. Spawn the project-steward subagent (Task) to verify release readiness:
    • Conventional commits since last release are well-formed (commitlint) and the implied bump (feat→minor, fix/perf→patch, BREAKING CHANGE→minor while 0.x) is correct.
    • Version files are in sync (scripts/sync-tauri-version.cjs) — a mismatch is CRITICAL.
    • Changelog/notes accurate; updater manifest (latest.json) + signing integrity (defer the security lens to tauri-security-reviewer).
  4. Do NOT manually tag or bump — releases are manually dispatched (Actions → "🚀 Release"); semantic-release then derives the bump from the commit types. Nothing runs automatically on push to main. Report blockers; fix commit/version issues via a PR.
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.

  1. 11d ago First seen · 20 lines · 20 tokens per session scan A 4f912622bb3f

Subscribe to this mod's changes

prepare-release is a command published in the GitHub repository saeedkolivand/ai-job-hunter-app (54 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 450 once invoked, about $0.0001 per session on Opus 5. 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.

Code reviewGit and workflowReactRustaijob-searchresume-buildertauri
Related

Other commands, from other repositories

rmslop

Check the diff against dev, and remove all AI generated slop introduced in this branch.

kylepelham/Drift · 5 tokens

advanced-code-review-context

Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.

axiomantic/spellbook · 19 tokens

review

Recent git commits: !git log --oneline -10.

jjmartres/ai-coding-agents · 3 tokens

check-pr

Check a PR's CI status, reviews, comments, and merge readiness.

Sagargupta16/claude-skills · 14 tokens

extend

Capture a mid-PR sub-idea and implement it onto the current open PR's branch — no new branch, no new PR. Preserves Verify → Review → Deliver.

lugassawan/swe-workbench · 35 tokens

pr

Prepare GitHub Pull Request with essential details.

hackermanishackerman/claude-skills-vault · 10 tokens