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/fanfan-de/anyboxWrote 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/fanfan-de/anybox/build-and-run-macos-app)<a href="https://agentmods.dev/commands/fanfan-de/anybox/build-and-run-macos-app"><img src="https://agentmods.dev/badge/commands/fanfan-de/anybox/build-and-run-macos-app/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/fanfan-de/anybox/build-and-run-macos-app"><img src="https://agentmods.dev/badge/commands/fanfan-de/anybox/build-and-run-macos-app.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.00000 | $0.00435 |
| Opus 5 | $0.00000 | $0.00217 |
| Sonnet 5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
build-and-run-macos-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 12d 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
/build-and-run-macos-app
Create or update the project-local macOS build_and_run.sh script, wire the
Codex app Run button, then use that script as the default build/run entrypoint.
Arguments
scheme: Xcode scheme name (optional)workspace: path to.xcworkspace(optional)project: path to.xcodeproj(optional)product: SwiftPM executable product name (optional)mode:run,debug,logs,telemetry, orverify(optional, default:run)app_name: process/app name to stop before relaunching (optional)
Workflow
- Detect whether the repo uses an Xcode workspace, Xcode project, or SwiftPM package.
- If the workspace is not inside git yet, run
git initat the project root so Codex app git-backed features unlock. - Create or update
script/build_and_run.shso it always stops the current app, builds the macOS target, and launches the fresh result. - For SwiftPM, keep raw executable launch only for true CLI tools; for AppKit/SwiftUI GUI apps, create a project-local
.appbundle and launch it with/usr/bin/open -n. - Support optional script flags for
--debug,--logs,--telemetry, and--verify. - Follow the canonical bootstrap contract in
../skills/build-run-debug/references/run-button-bootstrap.mdfor the exact script shape and.codex/environments/environment.tomlformat. - Run the script in the requested mode and summarize any build, script, or launch failure.
Guardrails
- Do not initialize a nested git repo inside an existing parent checkout.
- Do not leave stale
Runactions pointing at old script paths. - Keep the no-flag script path simple: kill, build, run.
- Use
--debug,--logs,--telemetry, or--verifyonly when the user asks for those modes.
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.
- 12d ago First seen · 31 lines · 0 tokens per session scan A ed7cfae2db75
build-and-run-macos-app is a command published in the GitHub repository fanfan-de/anybox (57 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 435 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.
Other commands, from other repositories
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.
initialize-ios
Manual override: initialize ast-index for iOS/Swift/ObjC project.
maestro-selectors-instructions
Guide to using Maestro selectors for targeting UI elements in tests.
mobile-performance-check
Analyze mobile app for performance issues using the mobile-best-practices database.
flutter-review
Review Flutter/Dart code for idiomatic patterns, widget best practices, state management, performance, accessibility, and security. Invokes the flutter-reviewer agent.
flutter-test
Run Flutter/Dart tests, report failures, and incrementally fix test issues. Covers unit, widget, golden, and integration tests.