Borrowing it
Nothing to install: this file belongs to baddonkey/exif-turbo. 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/baddonkey/exif-turbo/main/.github/prompts/release.prompt.mdgit clone --depth 1 https://github.com/baddonkey/exif-turboWrote 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/baddonkey/exif-turbo/release)<a href="https://agentmods.dev/commands/baddonkey/exif-turbo/release"><img src="https://agentmods.dev/badge/commands/baddonkey/exif-turbo/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/commands/baddonkey/exif-turbo/release"><img src="https://agentmods.dev/badge/commands/baddonkey/exif-turbo/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.00022 | $0.00430 |
| Opus 5.5 | $0.00009 | $0.00172 |
| Sonnet 5.5 | $0.00004 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
Release exif-turbo 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 15d 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
Cut a new release of exif-turbo.
Inputs
The user has provided (or will confirm) a release target: $ARGUMENTS
Accepted values:
patch,minor,major(auto-increment from current__version__)- explicit version
x.y.z - explicit triplet
major minor patch
Steps
-
Verify working tree is clean
- Run
git status --short. If there are uncommitted changes, ask the user to commit or stash first.
- Run
-
Prepare release PR (Windows)
- Run the PR-prep stage with the provided release target:
python scripts/release_windows.py $ARGUMENTS --stage prepare-pr
- This stage bumps version metadata, commits, pushes the current branch, and opens/reuses a PR to
main. - It must not run on
main.
- Run the PR-prep stage with the provided release target:
-
Stop and wait for merge
- Tell the user to merge the PR through the normal review process.
- Do not push
maindirectly.
-
Publish after merge (Windows)
- After the PR is merged and local
mainis up to date, run:python scripts/release_windows.py <resolved-version> --stage publish
- Publish requires an explicit resolved version (
x.y.zormajor minor patch), notpatch/minor/major.
- After the PR is merged and local
-
macOS/Linux asset updates (optional)
- macOS:
python scripts/update_macos_release.py(or--tag v<version>if needed) - Linux:
python scripts/update_linux_release.py --tag v<version>
- macOS:
-
Summary
- Confirm PR URL, merged state, pushed tag, release URL, and uploaded artifacts.
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.
- 15d ago First seen · 45 lines · 22 tokens per session scan A c9912afc2ec9
Release exif-turbo is a command published in the GitHub repository baddonkey/exif-turbo (11 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 430 once invoked, about $0.0001 per session on Opus 5.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-10-14.
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-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
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.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.