What is setup-updates?

A setup command that adds automatic update checks to an existing JUCE audio-plugin project. It uses Sparkle on macOS and WinSparkle on Windows, with installers distributed for each platform.

Use it to add a “Check for Updates...” menu item, background update checks, signed releases, and update-feed generation to the project’s standalone application.

It removes the need to design the update system and its release-signing setup by hand. It also provides a doctor mode for checking whether an existing update configuration has problems.

setup-updates — Command for Claude Code by danielraffel

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/danielraffel/generous-corp-marketplace

agentmods

npx agentmods add commands/danielraffel/generous-corp-marketplace/setup-updates

Made for: Claude Code.

Or install juce-dev, the plugin that ships this one along with the rest of its 3 skills, 10 commands.

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

README.md

[![agentmods](https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/setup-updates.svg)](https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/setup-updates)

Your own site

<a href="https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/setup-updates"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/setup-updates.svg" alt="Measured on agentmods" height="20"></a>

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

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

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00017	$0.02443
Opus 5	$0.00009	$0.01222
Sonnet 5	$0.00003	$0.00489
Haiku 4.5	$0.00002	$0.00244

Measured 7d ago against content hash de4e092c235a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

setup-updates 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 7d 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.

{check or cross} Feed URL is reachable (curl -s -o /dev/null -w "%{http_code}")

plugins/juce-dev/commands/setup-updates.md · 277 lines

How it starts

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

Setup Auto-Updates

Add in-app auto-update support to an existing JUCE-Plugin-Starter project. Uses Sparkle 2.x on macOS and WinSparkle on Windows.

Arguments

--doctor: Validate existing auto-update configuration and report issues
--help: Show help reference and stop

Implementation

Step 0: Handle --help

If --help is in the arguments, display this reference and stop:

juce-dev:setup-updates — Add auto-update support to a JUCE plugin project

Adds Sparkle 2.x (macOS) or WinSparkle (Windows) auto-update support to the
Standalone target. Updates are distributed as full-product installers (PKG on
macOS, Inno Setup on Windows).

After setup:
  - "Check for Updates..." appears in the Standalone app menu
  - Background update checks run automatically (configurable)
  - /juce-dev:build publish includes EdDSA signing and appcast generation

USAGE:
  /juce-dev:setup-updates              Run setup wizard
  /juce-dev:setup-updates --doctor     Validate existing setup
  /juce-dev:setup-updates --help       Show this reference

PREREQUISITES:
  - JUCE-Plugin-Starter project with .env and CMakeLists.txt
  - GitHub repository configured (GITHUB_USER and GITHUB_REPO in .env)

Do NOT proceed to the setup steps. Just display the help and return.

Step 1: Verify Project

Check that .env, CMakeLists.txt, and scripts/build.sh exist in the current directory.
- If missing: "This command must be run from a JUCE-Plugin-Starter project root."
Check if auto-updates are already configured:
- If .env contains ENABLE_AUTO_UPDATE=true and Source/AutoUpdater.h exists, tell the user auto-updates are already set up and offer to reconfigure.
Check that GITHUB_USER and GITHUB_REPO are set in .env:
- If missing: "Auto-updates require a GitHub repository. Set GITHUB_USER and GITHUB_REPO in .env first."

Step 2: Confirm Setup

question: "Add auto-update support to this project?"
header: "Auto-Updates"
options:
  - label: "Yes, add auto-updates (Recommended)"
    description: "Adds Sparkle (macOS) / WinSparkle (Windows) with EdDSA-signed updates via GitHub Releases"
  - label: "Cancel"
    description: "No changes will be made"

Read the full file on GitHub · 277 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.

7d ago First seen · 277 lines · 17 tokens per session scan A de4e092c235a

Subscribe to this mod's changes

setup-updates is a command published in the GitHub repository danielraffel/generous-corp-marketplace (11 stars, last pushed 8d ago), licensed MIT. It adds 17 tokens to every session and 2,443 once invoked, about $0.0001 per session on Opus 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-08-30.

Git and workflow Releases

land

Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).

gmickel/flow-next · 25 tokens

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.

OpenHands/extensions · 44 tokens

ship

Ship is the operational release-prep flow for a connected project repo.

robotaitai/project-bedrock · 0 tokens

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.

alisunstar/OpenSunstar · 0 tokens

release

Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.

terrene-foundation/kailash-coc-claude-py · 0 tokens

create-pr

Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.

dsswift/ion · 25 tokens

setup-updates