Borrowing it
Nothing to install: this file belongs to Iron-Ham/XcodePreviews. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Iron-Ham/XcodePreviews/main/CLAUDE.mdgit clone --depth 1 https://github.com/Iron-Ham/XcodePreviewsWrote 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/instructions/iron-ham/xcodepreviews/claude-md)<a href="https://agentmods.dev/instructions/iron-ham/xcodepreviews/claude-md"><img src="https://agentmods.dev/badge/instructions/iron-ham/xcodepreviews/claude-md.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.00695 | $0.00695 |
| Opus 5 | $0.00347 | $0.00347 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
XcodePreviews CLAUDE.md 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PreviewBuild - SwiftUI Preview Capture Toolkit
A toolkit for building and capturing SwiftUI previews for visual analysis.
Quick Start
# Standalone Swift file (no external dependencies)
./scripts/preview MyView.swift
# File in an Xcode project (auto-injects PreviewHost target)
./scripts/preview ContentView.swift --project MyApp.xcodeproj
# File in an SPM package
./scripts/preview Sources/Module/MyView.swift
# Just capture current simulator
./scripts/preview --capture-only
How It Works
Project Types & Approaches
| Project Type | Approach | Build Time | Script |
|---|---|---|---|
| Standalone Swift | Minimal host app | ~5 seconds | preview-minimal.sh |
| Xcode project | Dynamic target injection | ~3-4 seconds | preview-tool |
| SPM package | Temporary project creation | ~20 seconds | preview-tool |
Dynamic Preview Injection
For Xcode projects, the toolkit:
- Parses the Swift file to extract
#Preview { }content - Injects a temporary
PreviewHosttarget into the project - Configures dependencies based on imports
- Detects and includes resource bundles (Tuist, standard naming)
- Builds only the required modules
- Captures screenshot
- Cleans up the injected target
This is much faster than building a full app scheme.
Scripts & Tools
| Path | Purpose |
|---|---|
scripts/preview |
Unified entry point - auto-detects best approach |
scripts/preview-minimal.sh |
Build standalone Swift files |
scripts/xcode-preview.sh |
Build full Xcode project schemes |
scripts/capture-simulator.sh |
Screenshot current simulator |
scripts/sim-manager.sh |
Simulator management |
tools/preview-tool |
Swift CLI for dynamic preview injection, SPM preview, dependency resolution |
Usage Examples
Standalone Swift File
./scripts/preview templates/StandalonePreview.swift
Xcode Project with #Preview
./scripts/preview Modules/Components/Chip/Chip.swift \
--project MyApp.xcodeproj
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 · 110 lines · 695 tokens per session scan A 263b7dbb8d35
XcodePreviews CLAUDE.md is an instructions file published in the GitHub repository Iron-Ham/XcodePreviews (151 stars, last pushed 2mo ago), licensed MIT. It adds 695 tokens to every session, about $0.0035 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.