What is EXPORT-SIGNED-APP?

A release procedure for exporting a signed and notarized macOS app. Code signing identifies the developer, while notarization is Apple's security check for distributed apps.

Use it to update the app version, create a Release archive, sign it, notarize it, and build a distributable disk image.

It provides the required release steps and credentials setup so the app can be packaged for distribution correctly.

EXPORT-SIGNED-APP — Command by dep

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/dep/agent-rules/export-signed-app

Clone the repo

git clone --depth 1 https://github.com/dep/agent-rules

Made for: Codex.

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,544 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. 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.01544
Opus 5	$0.00000	$0.00772
Sonnet 5	$0.00000	$0.00309
Haiku 4.5	$0.00000	$0.00154

Measured 2d ago against content hash d6b3e7955b12, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

EXPORT-SIGNED-APP 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 2d 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.

.agents/commands/EXPORT-SIGNED-APP.md · 161 lines

How it starts

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

Export Signed App

Description

Export a signed and notarized macOS app for distribution.

Prerequisites

A valid Developer ID Application certificate with private key installed in your login keychain
A configured notarytool keychain profile named notarytool (see Setup below)
project.yml must remain the source of truth for release signing settings
create-dmg installed: brew install create-dmg

Setup: Store Notarization Credentials

APPLE_EMAIL and APPLE_APP_PASSWORD are in the project's .env file. Run this once to store them in the keychain:

source .env && xcrun notarytool store-credentials "notarytool" \
  --apple-id "$APPLE_EMAIL" \
  --team-id "299R8V27FZ" \
  --password "$APPLE_APP_PASSWORD"

Step-by-Step

0. Update the project's version number, incrementing the patch version unless told it's a minor or major release.

# in macOS/<AppName>/Info.plist
<key>CFBundleShortVersionString</key>
<string>x.y.z</string>

1. Create a signed Release archive

xcodegen generate && \
xcodebuild archive \
  -project "<AppName>.xcodeproj" \
  -scheme "<AppName>" \
  -configuration Release \
  -destination "generic/platform=macOS" \
  -archivePath "/tmp/<AppName>.xcarchive"

2. Export the signed .app

Create an export options plist:

cat > /tmp/export-options.plist << 'EOF'
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>method</key>
    <string>developer-id</string>
    <key>signingStyle</key>
    <string>automatic</string>
    <key>stripSwiftSymbols</key>
    <true/>
</dict>
</plist>
EOF

xcodebuild -exportArchive \
  -archivePath /tmp/<AppName>.xcarchive \
  -exportPath /tmp/<AppName>-export \
  -exportOptionsPlist /tmp/export-options.plist

3. Submit, wait, and staple

Note: notarytool requires a zip/pkg/dmg — it rejects a bare .app. Zip first, submit the zip, then staple the .app.

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

2d ago First seen · 161 lines · 0 tokens per session scan A d6b3e7955b12

Subscribe to this mod's changes

EXPORT-SIGNED-APP is a command published in the GitHub repository dep/agent-rules (11 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,544 tokens. 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-08-30.

Git and workflow Security ai-agents

EXPORT-SIGNED-APP

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Export Signed App

Description

Prerequisites

Setup: Store Notarization Credentials

Step-by-Step

0. Update the project's version number, incrementing the patch version unless told it's a minor or major release.

1. Create a signed Release archive

2. Export the signed .app

3. Submit, wait, and staple

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement