An automated procedure for creating a new Remarc software release through GitHub Actions, a service that runs tasks from a repository. It checks the current version, build number, recent releases, and appcast before asking for release details.

Use it to prepare a Remarc release, choose valid version and build numbers, and provide correctly formatted release notes.

It prevents version or build numbers from being reused and ensures release notes follow the format required for the update feed. This avoids releases failing or showing empty notes in the updater.

release — Command by metedata

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/metedata/remarc/release

Clone the repo

git clone --depth 1 https://github.com/metedata/Remarc

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,476 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00000	$0.01476
Opus 5	$0.00000	$0.00738
Sonnet 5	$0.00000	$0.00295
Haiku 4.5	$0.00000	$0.00148

Measured yesterday against content hash 72c4f98be7bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 yesterday.

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.

- Check the release asset is accessible: `curl -sIL https://github.com/metedata/Remarc/releases/download/vVERSION/Remarc.zip | head -1`

.claude/commands/release.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Remarc

Create a new Remarc release using the automated GitHub Actions workflow.

Instructions

When the user invokes this command, help them create a new release by:

Check current version - Read app/Config/Shared.xcconfig to get the current MARKETING_VERSION and CURRENT_PROJECT_VERSION
Check recent releases and appcast - Run git tag -l 'v*' | sort -V | tail -5 and inspect the live appcast. Neither the requested marketing version nor build number may already be advertised.
Prompt for release details - Ask the user for:
- Version number (e.g., "0.6.0") - must be an X.Y.Z semantic version higher than current
- Build number - must be higher than current (suggest next number)
- Release notes - what changed in this release
IMPORTANT: Release notes format Release notes MUST be formatted as bullet points starting with - for proper appcast generation:
```
- Fixed app hang issues during clipboard monitoring
- Improved performance
```
Plain paragraph text will result in EMPTY release notes in Sparkle's update dialog (the workflow fails the release if no - bullet is present). Keep them to about 3 high-level summary bullets, not a per-commit changelog.

Never rebuild an advertised version: the recreated public repository starts with source fields 0.5.1 / 12, but that shipped build is already in the appcast. The first source release must use a genuinely newer pair, such as 0.6.0 / 13.

Confirm and execute - Show the user what will happen:

Release Summary:
- Version: X.Y.Z (build N)
- Notes: [their notes]

This will:
1. Update version in Shared.xcconfig
2. Archive and export with Developer ID signing
3. Notarize with Apple
4. Sign update with EdDSA for Sparkle
5. Commit the version bump and push a `v$VERSION` tag
6. Create and verify a draft GitHub Release with Remarc.zip and Remarc.zip.sha256
7. Generate and validate the candidate appcast while the release is still a draft
8. Publish the release, then update appcast.xml on GitHub Gist

Read the full file on GitHub · 110 lines

Changes

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.

yesterday First seen · 110 lines · 0 tokens per session scan A 72c4f98be7bf

Subscribe to this mod's changes

release is a command published in the GitHub repository metedata/Remarc (66 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,476 tokens. 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-08-30.

Data and AI Git and workflow Mobile ai-agents developer-tools macos model-context-protocol screen-annotation swift

release

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Makes network callslowCapability

How it starts

Release Remarc

Instructions

What this file has done since we first saw it

Other commands, from other repositories

capture

click

see

agent

app

bridge