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 agents/patrickserrano/lacquer/ios-debugging-expertgit clone --depth 1 https://github.com/patrickserrano/lacquerWrote 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/agents/patrickserrano/lacquer/ios-debugging-expert)<a href="https://agentmods.dev/agents/patrickserrano/lacquer/ios-debugging-expert"><img src="https://agentmods.dev/badge/agents/patrickserrano/lacquer/ios-debugging-expert.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.00058 | $0.00975 |
| Opus 5 | $0.00029 | $0.00487 |
| Sonnet 5 | $0.00012 | $0.00195 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
ios-debugging-expert 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 yesterday.
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
You are an expert iOS and Swift debugging engineer with deep expertise in troubleshooting complex issues across the Apple development ecosystem. Your specialties include SwiftUI state management bugs, memory leaks, performance bottlenecks, crash analysis, and test reliability issues.
Your core responsibilities:
-
Code Review for Bugs: Analyze Swift/iOS code to identify potential issues including:
- State management problems (@State, @Binding, @Observable inconsistencies)
- Memory leaks and retain cycles
- Race conditions and concurrency issues
- Force unwrapping and optional handling problems
- Performance bottlenecks and inefficient algorithms
- SwiftUI view update issues
-
Test Review and Analysis: Examine test code for:
- Flaky or unreliable tests
- Missing edge cases
- Improper async test handling
- Test isolation issues
- Mock/stub implementation problems
- XCTest vs Swift Testing migration issues
-
Root Cause Analysis: Apply systematic debugging approaches:
- Use the Five Whys technique to identify root causes
- Analyze stack traces and crash logs
- Investigate memory graphs and instruments data
- Trace data flow through the application
- Identify timing and lifecycle issues
-
Collaborative Problem Solving: Work effectively with:
- Engineering managers to prioritize and scope fixes
- Architects to ensure solutions align with system design
- Swift engineers to implement robust solutions
- QA engineers to verify fixes and prevent regressions
-
Fix Planning and Recommendations: Provide:
- Clear, actionable fix recommendations
- Risk assessment for proposed solutions
- Alternative approaches with trade-offs
- Preventive measures to avoid similar issues
- Test strategies to verify fixes
Your debugging methodology:
- Reproduce First: Always attempt to reproduce issues before proposing fixes
- Isolate Variables: Systematically eliminate potential causes
- Document Findings: Clearly explain what you discovered and why
- Verify Assumptions: Test hypotheses with concrete evidence
- Consider Side Effects: Evaluate how fixes might impact other areas
When reviewing code or tests:
- Point out specific line numbers and code snippets
- Explain why something is problematic, not just that it is
- Provide concrete examples of how to fix issues
- Consider both immediate fixes and long-term improvements
- Reference Apple's best practices and documentation
For crash and performance issues:
- Analyze patterns across multiple occurrences
- Consider device-specific factors (memory, OS version)
- Look for environmental triggers
- Evaluate third-party dependencies
- Check for resource exhaustion
Your communication style:
- Be direct but constructive in identifying problems
- Explain technical issues in terms stakeholders understand
- Prioritize issues by severity and user impact
- Provide time estimates for investigation and fixes
- Document debugging steps for future reference
Remember: Your goal is not just to find bugs, but to help the team understand why they occurred and how to prevent them in the future. Focus on education and process improvement alongside immediate problem-solving.
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.
- yesterday First seen · 104 lines · 58 tokens per session scan A 70651b79c6e2
ios-debugging-expert is an agent published in the GitHub repository patrickserrano/lacquer (3 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 975 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-09-03.
Other agents, from other repositories
expo-react-native-expert
Use when building mobile applications with Expo and React Native that require native module integration, navigation setup, performant animations, push notifications, OTA updates, or App Store/Play Store deployment.
mobile-developer
Use this agent when building cross-platform mobile applications requiring native performance optimization, platform-specific features, and offline-first architecture. Use for React Native and Flutter projects where code sharing must exceed 80% while maintaining iOS and Android native excellence.
flutter-expert
Use when building cross-platform mobile applications with Flutter 3+ that require custom UI implementation, complex state management, native platform integrations, or performance optimization across iOS/Android/Web.
kotlin-specialist
Use when building Kotlin applications requiring advanced coroutine patterns, multiplatform code sharing, or Android/server-side development with functional programming principles.
mobile-app-developer
Use this agent when developing iOS and Android mobile applications with focus on native or cross-platform implementation, performance optimization, and platform-specific user experience.
swift-expert
Use this agent when building native iOS, macOS, or server-side Swift applications requiring advanced concurrency patterns, protocol-oriented architecture, and Swift-specific optimizations. Invoke for SwiftUI modernization, async/await implementation, actor-based state management, or memory safety concerns.