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-linux.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-linux)<a href="https://agentmods.dev/commands/baddonkey/exif-turbo/update-linux"><img src="https://agentmods.dev/badge/commands/baddonkey/exif-turbo/update-linux/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-linux"><img src="https://agentmods.dev/badge/commands/baddonkey/exif-turbo/update-linux.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.00513 |
| Opus 5.5 | $0.00010 | $0.00205 |
| Sonnet 5.5 | $0.00005 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
Update Linux packages on existing 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 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
Rebuild the Linux DEB and RPM packages for an existing release using containerised builds, and upload them, replacing any previous Linux assets.
Inputs
Target version (tag): $ARGUMENTS
Steps
-
Verify the release exists
- Run:
gh release view v<version> --repo baddonkey/exif-turbo - If the release is not found, stop and tell the user.
- Run:
-
Build the DEB package (runs inside an Ubuntu 24.04 Podman container)
- Run:
python scripts/build_deb.py - Translation catalogs are compiled automatically inside the container — do NOT touch .po files.
- Expected output artifact:
dist/exif-turbo-<version>-linux-amd64.deb - If the build fails, stop and show the error.
- Run:
-
Build the RPM package (runs inside an AlmaLinux 9 Podman container)
- Run:
python scripts/build_rpm.py - Expected output artifact:
dist/exif-turbo-<version>-linux-x86_64.rpm - If the build fails, stop and show the error.
- Run:
-
Delete any existing Linux assets on the release
- List current assets:
gh release view v<version> --repo baddonkey/exif-turbo --json assets --jq '.assets[].name' - For each asset whose name ends with
.debor.rpm, delete it:gh release delete-asset v<version> <asset-name> --repo baddonkey/exif-turbo --yes
- List current assets:
-
Upload the new packages
gh release upload v<version> \ dist/exif-turbo-<version>-linux-amd64.deb \ dist/exif-turbo-<version>-linux-x86_64.rpm \ --repo baddonkey/exif-turbo \ --clobber -
Summary
- Confirm the asset names and sizes 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 · 49 lines · 25 tokens per session scan A 8769c112fae7
Update Linux packages 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 513 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.
doc-changelog
Generation and maintenance of the project changelog.