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.
npx skills add thewolffish/wolffish-app --skill xcodegit clone --depth 1 https://github.com/thewolffish/wolffish-appWrote 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/skills/thewolffish/wolffish-app/xcode)<a href="https://agentmods.dev/skills/thewolffish/wolffish-app/xcode"><img src="https://agentmods.dev/badge/skills/thewolffish/wolffish-app/xcode/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/skills/thewolffish/wolffish-app/xcode"><img src="https://agentmods.dev/badge/skills/thewolffish/wolffish-app/xcode.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.00051 | $0.02009 |
| Opus 5.5 | $0.00020 | $0.00804 |
| Sonnet 5.5 | $0.00010 | $0.00402 |
| Haiku 4.5 | $0.00005 | $0.00201 |
Grade A, and why
xcode 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 1mo 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
Xcode
Build, test and run an iOS app the way a developer does from the terminal, with
the output parsed so a failing build reads as File.swift:42: message rather than
a thousand lines of log.
How to use
xcode_discover folder=<working folder>— finds the.xcworkspace/.xcodeproj(and tells you when the project is Flutter, Expo, React Native or Gradle instead, with the run path for each).xcode_schemes project=<path>— pick the app scheme.xcode_defaults {project, scheme, device}once. Every later call uses them.xcode_run— build, boot, install, launch. Then look at it with themobilecapability (mobile_use device=<udid>,mobile_indicator_on,mobile_screenshot,mobile_log).- Fix what
BUILD_FAILEDlists (dedupedfile:line: message, first 25) and run again.xcode_test only=Target/Class/testiterates on one test.
Where things land
- Derived data:
<workspace>/files/derived-data/<scheme>/(the.appunderBuild/Products/<Configuration>-iphonesimulator/). - Full xcodebuild logs:
<workspace>/files/xcode/logs/<build|test>-<scheme>-<time>.log—file_readthe log when the parsed errors are not enough.
Behaviour worth knowing
- Success is decided by xcodebuild's exit code, never by "BUILD SUCCEEDED" in the log.
- Builds are capped at 20 minutes (tests 30) and killed with
BUILD_STALLEDafter 5 minutes without output. Stopping the run kills xcodebuild. - A
devicethat looks like a UUID is passed asid=; anything else asname=. - Bundle ids are cached for 10 minutes per (project, scheme, configuration).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 188 lines · 51 tokens per session scan A f89afca617fe
xcode is a skill published in the GitHub repository thewolffish/wolffish-app (5 stars, last pushed 17d ago), licensed MIT. It adds 51 tokens to every session and 2,009 once invoked, about $0.0002 per session on Opus 5.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-09-16.
Other skills, from other repositories
agent-device
Automates Apple-platform apps (iOS, tvOS, macOS), Android devices, and Amazon Vega OS TV apps in Vega Virtual Devices. Use when navigating apps, taking snapshots/screenshots where supported, driving TV remotes, tapping, typing, scrolling, extracting UI info, collecting evidence, or planning agent-device CLI commands.
android-emulator
Verify and debug native, React Native, Expo, or Flutter apps on an Android Emulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an Android virtual device.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
verify-ui-change-in-cloud
Verifies user-facing Warp client changes by spawning a cloud agent with computer use to test Warp. Use only when the user explicitly requested computer-use verification or accepted an offer to run it, and ONLY in non-sandboxed environments and local environments. Triggers a cloud agent that runs the test-warp-ui skill.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.