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 skills add dagba/ios-mcp --skill vip-clean-architecturegit clone --depth 1 https://github.com/dagba/ios-mcpWrote 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/skills/dagba/ios-mcp/vip-clean-architecture)<a href="https://agentmods.dev/skills/dagba/ios-mcp/vip-clean-architecture"><img src="https://agentmods.dev/badge/skills/dagba/ios-mcp/vip-clean-architecture/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dagba/ios-mcp/vip-clean-architecture"><img src="https://agentmods.dev/badge/skills/dagba/ios-mcp/vip-clean-architecture.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.03648 |
| Opus 5 | $0.00026 | $0.01824 |
| Sonnet 5 | $0.00010 | $0.00730 |
| Haiku 4.5 | $0.00005 | $0.00365 |
Grade A, and why
vip-clean-architecture 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 10d 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 — 499 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VIP Clean Architecture
Overview
VIP (View-Interactor-Presenter) is Uncle Bob's Clean Architecture applied to iOS with strict unidirectional data flow. Unlike MVVM (bidirectional) or VIPER (complex 5-component), VIP uses 3 core components with protocol-based boundaries.
Core Principle: Data flows in one direction: View → Interactor → Presenter → View. No component ever calls backward in the cycle.
When to Use VIP
digraph vip_decision {
"Enterprise app?" [shape=diamond];
"Max testability?" [shape=diamond];
"Complex business logic?" [shape=diamond];
"Team > 3 devs?" [shape=diamond];
"Use VIP" [shape=box, style=filled, fillcolor=lightgreen];
"Use MVVM" [shape=box, style=filled, fillcolor=lightblue];
"Enterprise app?" -> "Max testability?" [label="yes"];
"Enterprise app?" -> "Use MVVM" [label="no"];
"Max testability?" -> "Use VIP" [label="yes"];
"Max testability?" -> "Complex business logic?" [label="no"];
"Complex business logic?" -> "Team > 3 devs?" [label="yes"];
"Complex business logic?" -> "Use MVVM" [label="no"];
"Team > 3 devs?" -> "Use VIP" [label="yes"];
"Team > 3 devs?" -> "Use MVVM" [label="no"];
}
Use VIP for:
- Enterprise iOS apps with strict quality requirements
- Features requiring 80%+ test coverage
- Complex business logic with multiple edge cases
- Multi-team projects needing clear boundaries
- Apps where testability > development speed
Use MVVM instead for:
- Standard iOS apps (most apps)
- Rapid prototyping or MVPs
- Simple CRUD applications
- Small teams (1-2 developers)
- Projects prioritizing delivery speed
VIP Components
| Component | Responsibility | Testability | What It Must NOT Do |
|---|---|---|---|
| View | Display, user input, lifecycle events | UI tests only | Business logic, formatting, navigation |
| Interactor | Business logic, use cases, orchestration | 100% unit testable | UI updates, data formatting, navigation |
| Presenter | Format data for display, prepare view models | 100% unit testable | Business logic, network calls, persistence |
| Worker | External services (network, DB, APIs) | Mock/stub in tests | Business logic, data formatting |
| Router | Navigation, screen transitions | Integration tests | Business logic, data management |
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.
- 10d ago First seen · 499 lines · 52 tokens per session scan A 8928b159940c
vip-clean-architecture is a skill published in the GitHub repository dagba/ios-mcp (3 stars, last pushed 7mo ago), licensed MIT. It adds 52 tokens to every session and 3,648 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-31.
Other skills, from other repositories
swift-protocol-di-testing
Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.
android-unit-test
Guide for writing and converting Chromium Android unit tests across host Robolectric (chromejunittests) and on-device (chromepublicunittestapk) suites.
react-native-testing
Write tests using React Native Testing Library (RNTL) v13 and v14 (@testing-library/react-native). Use when writing, reviewing, or fixing React Native component tests. Covers: render, screen, queries (getBy/getAllBy/queryBy/findBy), Jest matchers, userEvent, fireEvent, waitFor, and async patterns. Supports v13 (React…
flutter-add-widget-test
Implement a component-level test using WidgetTester to verify UI rendering and user interactions (tapping, scrolling, entering text). Use when validating that a specific widget displays correct data and responds to events as expected.
mobiai-android-testing
Use when writing or running tests in an Android project — unit tests, UI tests, choosing the right framework and patterns.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.