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/update-dmg-arm.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/update-dmg-arm)<a href="https://agentmods.dev/commands/baddonkey/exif-turbo/update-dmg-arm"><img src="https://agentmods.dev/badge/commands/baddonkey/exif-turbo/update-dmg-arm/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/update-dmg-arm"><img src="https://agentmods.dev/badge/commands/baddonkey/exif-turbo/update-dmg-arm.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.00025 | $0.00647 |
| Opus 5.5 | $0.00010 | $0.00259 |
| Sonnet 5.5 | $0.00005 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
Update ARM DMG on existing release scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl -s -H "Authorization: token $TOKEN" "https://api.github.com/repos/baddonkey/exif-turbo/releases/tags/v<version>"` How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rebuild the macOS Apple Silicon (arm64) DMG for an existing release and upload it, replacing any previous ARM macOS asset.
Inputs
Target version (tag): $ARGUMENTS
Steps
-
Verify the release exists
- Retrieve release metadata via the GitHub API using the token from the
macOS keychain (
security find-internet-password -s github.com -w). curl -s -H "Authorization: token $TOKEN" "https://api.github.com/repos/baddonkey/exif-turbo/releases/tags/v<version>"- Capture the release ID and upload URL for later steps.
- If the release is not found, stop and tell the user.
- Retrieve release metadata via the GitHub API using the token from the
macOS keychain (
-
Compile .mo translation files — do NOT touch .po files.
- Run:
pybabel compile -d src/exif_turbo/i18n/locales -D exif_turbo
- Run:
-
Build the macOS ARM app bundle and DMG
- Run:
python scripts/build_macos.py --arch arm64 - This uses exif-turbo-macos-arm.spec with
target_arch='arm64'. - The expected output artifact is
dist/exif-turbo-<version>-macos-arm64.dmg. - If the build fails, stop and show the error.
- Run:
-
Delete any existing ARM macOS DMG asset on the release
- List current assets: parse the
assetsarray from the release metadata fetched in step 1. - For each asset whose name ends with
-macos-arm64.dmg, delete it:curl -X DELETE -H "Authorization: token $TOKEN" "https://api.github.com/repos/baddonkey/exif-turbo/releases/assets/<asset_id>"
- List current assets: parse the
-
Upload the new DMG
- Use the upload URL from step 1 (strip the
{?name,label}template suffix). - Upload without a
labelparameter — the filename must be the display name. - Asset name:
exif-turbo-<version>-macos-arm64.dmg
curl -H "Authorization: token $TOKEN" \ -H "Content-Type: application/octet-stream" \ --data-binary @dist/exif-turbo-<version>-macos-arm64.dmg \ "<upload_url>?name=exif-turbo-<version>-macos-arm64.dmg"- Verify the response is HTTP 201.
- Use the upload URL from step 1 (strip the
-
Summary
- Confirm the asset name and size visible on the release page.
- Print:
https://github.com/baddonkey/exif-turbo/releases/tag/v<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.
- 15d ago First seen · 54 lines · 25 tokens per session scan A dbdb178aa2b3
Update ARM DMG on existing release is a command published in the GitHub repository baddonkey/exif-turbo (11 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 647 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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.