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 memi-design/memi --skill build-swiftui-interfacegit clone --depth 1 https://github.com/memi-design/memiWrote 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/memi-design/memi/build-swiftui-interface)<a href="https://agentmods.dev/skills/memi-design/memi/build-swiftui-interface"><img src="https://agentmods.dev/badge/skills/memi-design/memi/build-swiftui-interface.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00045 | $0.00513 |
| Opus 5 | $0.00023 | $0.00257 |
| Sonnet 5 | $0.00009 | $0.00103 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
build-swiftui-interface 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 8d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build SwiftUI Interface
Use Memi to establish the Apple-platform contract before editing source. Pair this skill with OpenAI's build-ios-apps plugin skills when they are installed and the task needs simulator, profiling, App Intents, or detailed framework guidance.
Compact preflight
npx -y @memi-design/[email protected] ios brief --platform ios --intent "<task>" --detail compact --json
Inspect the actual project next: deployment target, Swift language mode, shared schemes, local components, assets, navigation, state ownership, test targets, and nearby implementation patterns.
File contract
Preview every generated byte before writing:
npx -y @memi-design/[email protected] ios scaffold FeatureName \
--kind screen \
--module AppModule \
--output-root Sources \
--tests-root Tests \
--json
Use --write only after the paths and source match the repository. Memi writes a spec, SwiftUI view, preview, screen model when needed, and Swift Testing file. It does not mutate .xcodeproj or .xcworkspace, and it refuses silent overwrites.
Implementation rules
- Reuse local SwiftUI components and semantic assets before adding primitives.
- Keep state ownership narrow; keep I/O and expensive work out of
body. - Define loading, empty, populated, error, Dynamic Type, VoiceOver, reduced-motion, and dark-appearance states.
- Gate newer APIs. Liquid Glass requires an iOS 26+ branch and a behaviorally equivalent fallback.
- Treat June 2026 APIs by their documented availability; do not invent an iOS version label.
- Preserve the existing architecture and project-generation workflow.
Verification receipt
Run the repository's canonical commands. When none exist, discover shared schemes and explicit destinations with xcodebuild -list -json and xcrun simctl list devices available, then build and test the smallest target.
Report exact commands, files, deployment assumptions, simulator flow, accessibility states, and anything not executed. A source review is not simulator proof, and a simulator build is not signing or App Store proof.
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.
- 8d ago First seen · 47 lines · 45 tokens per session scan A 34e63bd37528
build-swiftui-interface is a skill published in the GitHub repository memi-design/memi (40 stars, last pushed 4d ago), licensed MIT. It adds 45 tokens to every session and 513 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 skills, from other repositories
accessibility-per-component
Run an accessibility audit on a specific design system component. Trigger when someone says: accessibility check, a11y audit, WCAG compliance, is this accessible, check accessibility, does this meet WCAG, screen reader support, keyboard navigation check, or anything about auditing the accessibility of a specific…
schema-validator
Validate token files against DTCG 2025.10, Style Dictionary, or custom schemas. Trigger when someone says: validate token JSON, check my token files for errors, schema validation for tokens, are my token files valid, DTCG compliance check, validate token format, or anything about checking whether token files are…
fmcp-ds-audit-orchestrator
Figma ekranlarını 5 kategori açısından platform-agnostic denetler (DS compliance / a11y / drift / visual QA / impact). Read-only çalışır; bulguları raporlar, düzeltmeleri sadece önerir — mutation için onay + ayrı agent. Her platformda çalışır. Condensed-first: Essentials bölümü %80 case'i kapsar, Advanced sadece edge…
design-fidelity-verify
Prove a running app matches its design spec by measuring rendered values, not eyeballing a screenshot. Use when the user says "verify the design", "is this pixel-perfect", "check against Figma", "does the app match the design", or "design QA this screen". Runs a bounded vision+numeric loop over web or mobile…
xcforge
Complete reference for xcforge — 109 MCP tools + 113 CLI commands for iOS development. Covers build, test, simulator, physical devices, SPM, UI automation, screenshots, logs, git, visual regression, accessibility, localization, session profiles, diagnosis workflows, plan execution, LLDB debugger integration, bless…
design-qa
Internal prototype QA helper. Use only after a Product Design prototype, URL-to-code build, or image-to-code build has a source visual target and a rendered implementation to compare before handoff. Do not use for broad UX critique, design critique, product audits, or flow reviews; route those user-facing requests to…