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/strip-release-assets.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/strip-release-assets)<a href="https://agentmods.dev/commands/baddonkey/exif-turbo/strip-release-assets"><img src="https://agentmods.dev/badge/commands/baddonkey/exif-turbo/strip-release-assets/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/strip-release-assets"><img src="https://agentmods.dev/badge/commands/baddonkey/exif-turbo/strip-release-assets.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.00036 | $0.00415 |
| Opus 5.5 | $0.00014 | $0.00166 |
| Sonnet 5.5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
Strip Release Assets 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
Remove all binary assets from a GitHub release, leaving the release page and its notes intact.
Inputs
The target release tag is: $ARGUMENTS
Steps
-
Resolve the release
- Run:
gh release view $ARGUMENTS --json tagName,name,assets - Display the release name, tag, and the full list of assets (name + size) to the user.
- If no tag was provided or the release is not found, ask the user to supply the correct tag.
- Run:
-
Ask for confirmation
- Show the user exactly which assets will be deleted, e.g.:
The following assets will be permanently removed from release $ARGUMENTS: • exif-turbo-X.Y.Z-windows.msi (208 MB) • exif-turbo-X.Y.Z-macos.dmg (195 MB) The release page and its notes will NOT be deleted. Proceed? (yes / no) - Wait for explicit confirmation. Do NOT proceed if the answer is anything other than "yes".
- Show the user exactly which assets will be deleted, e.g.:
-
Delete each asset
- For each asset listed in step 1, run:
gh release delete-asset $ARGUMENTS "<asset-name>" --yes - Report each deletion as it completes.
- For each asset listed in step 1, run:
-
Verify
- Run:
gh release view $ARGUMENTS --json assets - Confirm the assets list is now empty (or list any that remain).
- Run:
-
Summary
- Report how many assets were removed and confirm the release page is still live at:
https://github.com/baddonkey/exif-turbo/releases/tag/$ARGUMENTS
- Report how many assets were removed and confirm the release page is still live at:
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 · 44 lines · 36 tokens per session scan A 48b7e26279f2
Strip Release Assets is a command published in the GitHub repository baddonkey/exif-turbo (11 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 415 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.