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 commands/carolanelfbv/ios-development-agents/analyzegit clone --depth 1 https://github.com/CarolaneLFBV/ios-development-agentsWrote 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/commands/carolanelfbv/ios-development-agents/analyze)<a href="https://agentmods.dev/commands/carolanelfbv/ios-development-agents/analyze"><img src="https://agentmods.dev/badge/commands/carolanelfbv/ios-development-agents/analyze.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.00013 | $0.00723 |
| Opus 5 | $0.00006 | $0.00362 |
| Sonnet 5 | $0.00003 | $0.00145 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
analyze 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 4d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ios:analyze - iOS Code Analysis & Review
Analyze $ARGUMENTS for performance, architecture, security, quality, and code review.
Delegation
Route by --focus, spawning specialists in parallel via the Task tool (one Task per specialist), then consolidate their findings into the output below:
security→ security-specialistperformance→ performance-specialistarchitecture→ architecture-specialistquality(default) or--review→ swift-specialist + swiftui-specialist
Arguments
| Flag | Values | Default | Description |
|---|---|---|---|
--focus |
performance|security|architecture|quality | quality | Analysis focus |
--review |
- | - | Code review mode |
--checklist |
- | - | Generate review checklist |
--score |
- | - | Include quality score (0-100) |
--pr |
- | - | PR review format |
--instruments |
- | - | Include Instruments recommendations |
--export |
<path> |
- | Export results |
Analysis Modes
| Mode | Output |
|---|---|
| Default | Deep analysis with findings |
--review |
Code review with suggestions |
--checklist |
Structured checklist output |
--score |
Numeric quality assessment |
--pr |
PR approve/request changes format |
Review Checklist (--checklist)
Swift Best Practices
- Uses
@ObservableoverObservableObject - Proper error handling (no force unwraps)
- Memory management (weak/unowned)
- Async/await over completion handlers
SwiftUI Patterns
-
LazyVStackfor lists - Proper state management
- Small, focused views
- Modern navigation APIs
Architecture
- Single responsibility
- Protocol-based abstractions
- Dependency injection
Security
- Keychain for sensitive data
- No hardcoded secrets
- Input validation
Quality Score (--score)
# Quality Score: 85/100
| Category | Score | Details |
|----------|-------|---------|
| Architecture | 90 | Clean separation |
| Performance | 80 | Minor optimizations |
| Security | 85 | Good practices |
| Maintainability | 85 | Clear code |
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.
- 4d ago First seen · 96 lines · 13 tokens per session scan A 1287134a8b10
analyze is a command published in the GitHub repository CarolaneLFBV/ios-development-agents (7 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 723 once invoked, about $0.0001 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-31.
Other commands, from other repositories
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.
build-verify
Run the full build / test / analyze / format verification pass for this Flutter app.
create-pr-from-staged-changes
You are helping to create a pull request following the iOS team's standard template.
apollo-status
Show the current Apollo removal migration progress.
ios-privacy
Prepare privacy labels, permissions, policy links, and data-use truth for iOS release.
initialize-ios
Manual override: initialize ast-index for iOS/Swift/ObjC project.