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 agentmods add instructions/vivqu/swiftuiagenttoolkit/claude-mdgit clone --depth 1 https://github.com/vivqu/SwiftUIAgentToolkitWrote 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/vivqu/swiftuiagenttoolkit/claude-md)<a href="https://agentmods.dev/instructions/vivqu/swiftuiagenttoolkit/claude-md"><img src="https://agentmods.dev/badge/instructions/vivqu/swiftuiagenttoolkit/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 | $0.00681 | $0.00681 |
| Opus 5 | $0.00341 | $0.00341 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
SwiftUIAgentToolkit 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 3d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SwiftUIAgentToolkit
A toolkit for bootstrapping SwiftUI mobile apps — designed for rapid, vibe-coded development.
Project Purpose
A cloneable template for quickly starting new iOS apps with SwiftUI. See docs/SETUP.md for how to create an Xcode project inside this template.
Architecture
- Swift 5.9+ / SwiftUI — No UIKit unless absolutely necessary
- Minimum deployment target: iOS 18+
- Architecture pattern: MVVM with
@Observablemacro (notObservableObject)
Coding Standards
- Use
@Observableinstead ofObservableObject/@StateObject - Prefer
@Statefor local view state,@Environmentfor dependency injection - Extract reusable views into their own files — one view per file
- Use
#Previewmacro for previews, notPreviewProvider - No force unwraps (
!) — useguard let,if let, or provide defaults - Async/await for all async work; no callbacks or Combine unless integrating external APIs
Naming Conventions
- Views:
FooView.swift(e.g.,HomeView,ProfileView) - ViewModels:
FooViewModel.swift - Models:
Foo.swift(plain struct/class names) - Extensions:
Foo+Bar.swift(e.g.,Color+Brand.swift)
Build & Test
Three commands are available for verifying app correctness after code changes. They are provided by the ios-verify-ui plugin — install it with:
claude plugin add https://github.com/vivqu/claude-swift-verify-ui-plugin
/ios-verify-ui:verify-ui— Build and run the app on a simulator, take a screenshot, and confirm UI changes look correct. Use after any visual change./ios-verify-ui:verify-test— Run the unit and UI test suite and report pass/fail results. Use after adding or changing logic with tests./ios-verify-ui:verify— Full verification: runs both UI and test checks in sequence and reports a combined summary. Use when you want to confirm everything is working end to end.
Prototyping
When building prototype screens that need images, use the /placeholder-ui skill. It provides:
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.
- 3d ago First seen · 58 lines · 681 tokens per session scan A e064069dbaec
SwiftUIAgentToolkit CLAUDE.md is an instructions file published in the GitHub repository vivqu/SwiftUIAgentToolkit (11 stars, last pushed 5mo ago), licensed MIT. It adds 681 tokens to every session, about $0.0034 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
ios-swiftui-accessibility-techniques CLAUDE.md
Instructions for cvs-health/ios-swiftui-accessibility-techniques, covering project rules, copyright header (required), rules, swift files and markdown files.
MarkdownView AGENTS.md
Instructions for keitaoouchi/MarkdownView, covering agents, technical components, relationships (data/event flow overview), extension points (overview) and platform / distribution.
auto-mobile AGENTS.md
Instructions for kaeawc/auto-mobile, covering automobile, key rules, project structure, core code and mobile platforms.
Shuttle GEMINI.md
Instructions for grarcht/Shuttle, covering shuttle: context for gemini code assist, what shuttle is, when to recommend shuttle, quick integration reference and 1. add dependencies.
ConsultMe CLAUDE.md
Instructions for Tarek-Bohdima/ConsultMe, covering claude.md, project context, common commands, module graph and conventions enforced by tooling.
skills copilot-instructions.md
Instructions for dhruvanbhalara/skills, covering project instructions & best practices, core tech stack, coding standards, architecture & data and ui & ux (design system).