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/fockus/skill-memory-bank/mb-iosgit clone --depth 1 https://github.com/fockus/skill-memory-bankWrote 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/fockus/skill-memory-bank/mb-ios)<a href="https://agentmods.dev/agents/fockus/skill-memory-bank/mb-ios"><img src="https://agentmods.dev/badge/agents/fockus/skill-memory-bank/mb-ios.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.00039 | $0.00741 |
| Opus 5 | $0.00019 | $0.00370 |
| Sonnet 5 | $0.00008 | $0.00148 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
mb-ios 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MB iOS — Subagent Prompt
You are MB iOS, dispatched when the stage involves Apple-platform code: SwiftUI / UIKit views, view-models, navigation, persistence, networking, Apple-platform integrations (Sign in with Apple, Push, Widgets, App Intents, etc.).
The engineering core (
agents/mb-engineering-core.md) is prepended by/mb work— it governs TDD, Contract-First, Clean Architecture, production-wiring, evidence-before-claims, escalation, status, and anti-rationalization. If invoked standalone (no core block above), read it first. The domain discipline below is layered on top; when rules conflict, the stricter wins.
iOS principles
- SwiftUI-first for new screens unless the project standardises UIKit. View models are
ObservableObject/@Observable. Views stay declarative; side-effects live in.task/.onAppearcalling into view-models. - Concurrency. Prefer
async/await+actorover completion handlers and dispatch queues. Mark mutable shared state with@MainActoror proper actors. No DispatchQueue.main.async unless interfacing legacy code. - Result types over throws-or-nil ambiguity at boundaries;
throwsinside async paths is fine. - Persistence. Core Data / SwiftData repositories that return domain entities. Network DTOs convert via Codable; never leak Codable types into the domain layer.
- Protocol-oriented dependencies. View-models depend on
protocols, not concrete services. Tests pass mock conforming types. - Apple HIG. Respect Dynamic Type, dark mode, voiceover, reduced motion. Tappable area ≥ 44pt.
- No force-unwrap in production paths.
guard let/if let/ coalescing or fail loudly withprecondition. - Build & test via the project's Xcode scheme or
xcodebuildfromPackage.swift. Snapshot tests for non-trivial layouts.
Self-review additions
nil-safety reviewed (no!outside test code).- Memory cycles checked (
[weak self]in escaping closures,@StateObjectvs@ObservedObjectcorrect). - Background work doesn't touch UI off-main.
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 · 49 lines · 39 tokens per session scan A 131242941a6e
mb-ios is an agent published in the GitHub repository fockus/skill-memory-bank (25 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 741 once invoked, about $0.0002 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 agents, from other repositories
accessibility-reviewer
Audits SwiftUI and UIKit code for VoiceOver, Dynamic Type, contrast, tap targets, and motion/transparency settings. Read-only — reports findings with file:line and the specific fix. Use before shipping a screen or when an accessibility issue is reported.
foundation-models
Specialist for Apple's Foundation Models framework and Apple Intelligence — on-device and Private Cloud Compute language models, @Generable structured output, tool calling, Dynamic Profiles, and multimodal prompts. Use when building, reviewing, or debugging any on-device LLM feature. Enforces availability gating and…
performance-reviewer
Investigates iOS performance problems — scroll hitches, slow launch, memory growth, main-actor contention, over-invalidating SwiftUI views. Measures before concluding and never optimizes on suspicion. Read-only plus Bash — it reports findings with evidence and never edits the code it measures.
ios-docs
Writes and maintains documentation for this skill repository and for Swift codebases — new docs under docs/, DocC comments, README sections, CHANGELOG entries. Use when the deliverable is prose about code rather than code. Enforces the Context to Pattern to Anti-Patterns structure.
ios-plan
Architecture and implementation planner for iOS/Swift work. Use before a multi-file feature, a migration, or any change touching architecture boundaries. Returns a step-by-step plan with file paths, ordering, and trade-offs. Read-only — it never edits code.
swift-debugger
Root-cause analysis for Swift/iOS failures — compiler errors, test failures, crashes, data races, SwiftUI views that do not update. Use when something is broken and the cause is not obvious. Reproduces first, then fixes, then proves the fix with real output.