Borrowing it
Nothing to install: this file belongs to Pranav-Karra-3301/tuck. 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/Pranav-Karra-3301/tuck/main/.cursor/commands/release.mdgit clone --depth 1 https://github.com/Pranav-Karra-3301/tuckWrote 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/pranav-karra-3301/tuck/release)<a href="https://agentmods.dev/commands/pranav-karra-3301/tuck/release"><img src="https://agentmods.dev/badge/commands/pranav-karra-3301/tuck/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.00005 | $0.00206 |
| Opus 5 | $0.00003 | $0.00103 |
| Sonnet 5 | $0.00001 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00021 |
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 6d 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
Check Version
Check current version.
node -p "require('./package.json').version"
Dry Run Release
Test semantic-release without publishing.
npx semantic-release --dry-run
Manual Release Trigger
Trigger release workflow manually (via GitHub UI or CLI).
gh workflow run release.yml
Check Release Status
Check the status of release workflow.
gh run list --workflow=release.yml
View Changelog
View the changelog.
cat CHANGELOG.md
Check NPM Package
Check if package is published on npm.
npm view @pranav-karra/tuck
Verify Commit Messages
Check recent commits follow conventional format.
git log --oneline -10
Each should start with: feat:, fix:, docs:, refactor:, test:, or chore:
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.
- 6d ago First seen · 62 lines · 5 tokens per session scan A c86d0f12078a
release is a command published in the GitHub repository Pranav-Karra-3301/tuck (15 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 206 once invoked, about $0.0000 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.
Other commands, from other repositories
hatch3r-release
Release-workflow orchestrator — preflight, SemVer bump, changelog sync, build + CycloneDX SBOM, adapter-output verification, quality gates, release-notes reconciliation, then stop before publish/merge for human approval.
create-release-note.en
Generate release notes from PRs and commits.
post-release.en
Read and execute the post-release skill from .agents/skills/post-release/SKILL.md.
release.en
Run the version release workflow.
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.
finish-branch-execute
Step 4 of finishing-a-development-branch: Execute chosen integration option (merge, PR, PR+dance, keep, or discard).