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.
git clone --depth 1 https://github.com/danielraffel/generous-corp-marketplaceWrote 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/danielraffel/generous-corp-marketplace/setup-ios)<a href="https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/setup-ios"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/setup-ios.svg" alt="Measured on agentmods" 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.00015 | $0.01675 |
| Opus 5 | $0.00008 | $0.00838 |
| Sonnet 5 | $0.00003 | $0.00335 |
| Haiku 4.5 | $0.00002 | $0.00168 |
Grade A, and why
setup-ios 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add iOS App Target
Add an iOS/iPadOS app target to an existing JUCE-Plugin-Starter project. Supports both standalone iOS app and AUv3 Audio Unit extension. Detects whether Visage GPU UI is enabled and creates the appropriate iOS app files.
Note: The macOS AUv3 format is already included in the default
FORMATSline in CMakeLists.txt (AU AUv3 VST3 Standalone). This command adds an iOS-specific app target that can host an AUv3 extension for use in iOS DAWs like AUM, GarageBand, or Cubasis.
Implementation
Step 1: Verify Project
-
Check that the current working directory is a JUCE-Plugin-Starter project:
CMakeLists.txtmust exist.envmust exist
-
If any are missing, tell the user this command must be run from a JUCE-Plugin-Starter project root.
-
Check if an iOS target already exists:
- If
CMakeLists.txtcontainsjuce_add_gui_appwith iOS configuration, tell the user an iOS target already exists.
- If
Step 2: Detect Visage Status
Check if Visage GPU UI is available:
- If
external/visage/directory exists AND.envcontainsUSE_VISAGE_UI=TRUE→ Visage mode - Otherwise → Plain JUCE mode
Step 3: Detect Project Configuration
Read .env to extract:
PROJECT_NAME(fallback: directory name)PROJECT_BUNDLE_ID(fallback:com.example.appname)COMPANY_NAME(fallback: "Company")
Read Source/PluginProcessor.h (if it exists) to understand the audio engine pattern.
Step 4: Confirm
question: "Add iOS app target to this project?"
header: "iOS"
options:
- label: "Yes, add iOS target (Recommended)"
description: "Creates App/ directory with iOS-specific files and updates CMakeLists.txt"
- label: "Cancel"
description: "No changes will be made"
If Visage mode, note: "Will use Visage GPU-accelerated UI (Metal rendering, native touch events)" If Plain JUCE mode, note: "Will use standard JUCE UI components"
Step 5: Create iOS App Files
Create the App/ directory with these files:
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.
- 8d ago First seen · 195 lines · 15 tokens per session scan A bfd553872fcd
setup-ios is a command published in the GitHub repository danielraffel/generous-corp-marketplace (11 stars, last pushed 9d ago), licensed MIT. It adds 15 tokens to every session and 1,675 once invoked, about $0.0001 per session on Opus 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-08-30.
Other commands, from other repositories
status
Show 3d-design team status and recent activity.
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.
play-dashboard
Play in the dashboard — the local viewer becomes your play surface, with a live AI DM beside it.
mobile-performance-check
Analyze mobile app for performance issues using the mobile-best-practices database.
flutter-test
Run Flutter/Dart tests, report failures, and incrementally fix test issues. Covers unit, widget, golden, and integration tests.
phaser-run
Start the Phaser dev server and verify the game boots.