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 markdavidgan/apple-dev-skills --skill build-cache-cleangit clone --depth 1 https://github.com/markdavidgan/apple-dev-skillsWrote 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/markdavidgan/apple-dev-skills/build-cache-clean)<a href="https://agentmods.dev/skills/markdavidgan/apple-dev-skills/build-cache-clean"><img src="https://agentmods.dev/badge/skills/markdavidgan/apple-dev-skills/build-cache-clean/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/markdavidgan/apple-dev-skills/build-cache-clean"><img src="https://agentmods.dev/badge/skills/markdavidgan/apple-dev-skills/build-cache-clean.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.00144 | $0.01196 |
| Opus 5.5 | $0.00058 | $0.00478 |
| Sonnet 5.5 | $0.00029 | $0.00239 |
| Haiku 4.5 | $0.00014 | $0.00120 |
Grade C, and why
build-cache-clean scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf path/to/repo/.build How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Cache Clean
Frees disk space by deleting regenerable build output, never source, device state, or model data. Every path here is gitignored and safe to delete — the next build/install recreates it.
Find the big offenders first
.build/ and Xcode build/ directories are invisible to a plain top-level du because they're dotfiles or nested — always check explicitly, per repo:
# Overall disk headroom
df -h /
# Per-repo SwiftPM + Xcode build dirs (the usual multi-GB culprits)
find ~/code -maxdepth 4 -type d \( -name ".build" -o -name "build" \) -exec du -sh {} \; 2>/dev/null
# Global Xcode caches (shared across all repos, not per-repo)
du -sh ~/Library/Developer/Xcode/DerivedData
du -sh ~/Library/Developer/Xcode/Archives
du -sh ~/Library/Developer/CoreSimulator/Caches
# Simulator device data (see caution below — usually NOT cache to clear)
du -sh ~/Library/Developer/CoreSimulator/Devices/*/
A repo's .build/ (SwiftPM module cache + resolved build products) and build/ (Xcode build products) commonly dwarf everything else in the tree combined — 50–100+ GB is normal for an actively developed multi-target app after months without a clean.
Safe to delete — regenerates on next build
# Per-repo SwiftPM build cache
rm -rf path/to/repo/.build
rm -rf path/to/repo/apps/<app>/.build
# Per-repo/target Xcode build products
rm -rf path/to/repo/apps/<app>/build
# Global Xcode DerivedData (shared cache across all Xcode projects)
rm -rf ~/Library/Developer/Xcode/DerivedData/*
# Global CoreSimulator caches (not device data — see below)
rm -rf ~/Library/Developer/CoreSimulator/Caches/*
Verify a path is actually gitignored before deleting if you didn't create it yourself:
git -C path/to/repo check-ignore -v .build build
Adjacent dev-tool caches, same trip
These aren't Apple-specific but pile up alongside Xcode caches on the same machine and are equally safe to clear:
npm cache clean --force
pnpm store prune # only removes unreferenced packages
pip cache purge
brew cleanup -s
rm -rf ~/Library/Caches/ms-playwright/* # browser binaries, redownload on demand
rm -rf ~/Library/Caches/<Browser>/* # e.g. "Microsoft Edge", "Google Chrome" render caches
rm -rf ~/Library/Caches/typescript/*
rm -rf ~/Library/Caches/node-gyp/*
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 · 97 lines · 144 tokens per session scan C 0de3d7cdda2b
build-cache-clean is a skill published in the GitHub repository markdavidgan/apple-dev-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 144 tokens to every session and 1,196 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
asc-revenuecat-catalog-sync
Reconcile App Store Connect subscriptions and in-app purchases with RevenueCat products, entitlements, offerings, and packages using asc and RevenueCat MCP. Use when setting up or syncing subscription catalogs across ASC and RevenueCat.
asc-localize-metadata
Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI. Use when asked to localize an app's App Store listing, translate app descriptions, or add new languages to App Store Connect.
asc-shots-pipeline
Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (asc screenshots frame), and screenshot upload (asc screenshots upload). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition…
asc-metadata-sync
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
asc-release-flow
Orchestrate App Store releases with asc, including staging a version, uploading or building an artifact, publishing, and submitting for review. Use when the user wants to prepare or execute a release. Keep Game Center item preparation in this skill; route other readiness failures, stuck submissions, cancellation, and…
asc-submission-health
Diagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions. Use when validation fails, a version is not in a valid state, review status is unclear or stuck, or a failed submission must be repaired and…