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 skills/minghinmatthewlam/agent-guards/ios-devnpx skills add minghinmatthewlam/agent-guards --skill ios-devgit clone --depth 1 https://github.com/minghinmatthewlam/agent-guardsWhat 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.00061 | $0.00466 |
| Opus 5 | $0.00030 | $0.00233 |
| Sonnet 5 | $0.00012 | $0.00093 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
ios-dev 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS Development
Use xcodebuildmcp for a fast simulator-first development loop. Prefer explicit project, scheme, and simulator flags so agent runs do not depend on hidden configuration.
Read references/commands.md when selecting exact discovery, simulator, device, logging, debugging, or Swift package commands.
Workflow
- Discover the project or workspace, schemes, and available simulators.
- Establish the smallest failing build, test, launch, or interaction.
- Fix one failure class at a time.
- Re-run the focused command.
- For runtime or UI behavior, reproduce in the running app and capture logs plus visible evidence.
- Run broader relevant tests after the focused path passes.
Use simulator-first unless hardware, signing, sensors, performance, or another device-specific contract requires a physical device.
Failure Triage
- Build/test: verify project, scheme, destination, configuration, and build settings before cleaning.
- Runtime: start focused log capture, reproduce, stop capture, and inspect the resulting logs.
- UI: inspect the accessibility snapshot and capture a screenshot or recording of the real interaction.
- Simulator state: verify boot and app state before considering reset.
- Device: confirm the exact device identifier and signing prerequisites.
Run xcodebuildmcp doctor when command availability or environment health is unclear.
Gotchas
- Cleaning is not a diagnosis; first capture the original failure.
- Simulator success does not prove device-only behavior.
- Build success does not prove launch or UI behavior.
- Ask before erasing a simulator or removing user data.
- Tool output and screenshots should identify the simulator/device and app state being proven.
- Verify current CLI help when a command or flag is rejected; tool interfaces can drift.
Closeout
Report the failing surface, root cause evidence, change made, exact verification commands or interaction, resulting state, and any device-only or signing risk that remains.
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.
- 3d ago First seen · 45 lines · 61 tokens per session scan A a5477d3d5881
ios-dev is a skill published in the GitHub repository minghinmatthewlam/agent-guards (36 stars, last pushed 14d ago), licensed MIT. It adds 61 tokens to every session and 466 once invoked, about $0.0003 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 skills, from other repositories
edge-to-edge
Use this skill to migrate your Jetpack Compose app to add adaptive edge-to-edge support and troubleshoot common issues. Use this skill to fix UI components (like buttons or lists) that are obscured by or overlapping with the navigation bar or status bar, fix IME insets, and fix system bar legibility.
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.
flutter-fix-layout-issues
Fixes Flutter layout errors (overflows, unbounded constraints) using Dart and Flutter MCP tools. Use when addressing "RenderFlex overflowed", "Vertical viewport was given unbounded height", or similar layout issues.
referral-program
When the user wants to design, launch, or optimize an in-app referral / invite / share-to-earn program — including reward structure, mechanics, fraud prevention, deep link setup, and viral coefficient measurement. Use when the user mentions "referral program", "invite a friend", "refer and earn", "share to earn"…
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
ios-hig-design
Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad layout", "SwiftUI", "UIKit", "Dynamic Island", "safe areas", "HIG compliance", "SF Symbols", "haptic feedback", "iOS accessibility", "make my app feel native", or "follow Apple design guidelines".…