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 patrickserrano/lacquer --skill update-swiftui-apisgit 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/skills/patrickserrano/lacquer/update-swiftui-apis)<a href="https://agentmods.dev/skills/patrickserrano/lacquer/update-swiftui-apis"><img src="https://agentmods.dev/badge/skills/patrickserrano/lacquer/update-swiftui-apis.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.1 | $0.00077 | $0.01262 |
| Opus 5 | $0.00039 | $0.00631 |
| Sonnet 5 | $0.00015 | $0.00252 |
| Haiku 4.5 | $0.00008 | $0.00126 |
Grade A, and why
update-swiftui-apis 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.
This is a copy
92% identical to update-swiftui-apis — 17 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update SwiftUI APIs
Systematically scan Apple's developer documentation via the Sosumi MCP, identify deprecated SwiftUI APIs and their modern replacements, and update ../swiftui-expert-skill/references/latest-apis.md (sibling skill directory, relative to this skill's own directory).
Prerequisites
- Sosumi MCP must be enabled and available (provides
searchAppleDocumentation,fetchAppleDocumentation,fetchAppleVideoTranscript,fetchExternalDocumentation). Verify before starting by callingsearchAppleDocumentationwith a trivial query (e.g.SwiftUI); if the tool is unavailable or errors, Sosumi is not usable. - If Sosumi is unavailable: stop and tell the user it's required. As a fallback, manually browse https://developer.apple.com/documentation/swiftui and relevant WWDC session pages for deprecation notices, citing them the same way Sosumi output would be cited, then continue from Step 4.
- Write access to this repository (or a fork)
Workflow
1. Understand current coverage
Read ../swiftui-expert-skill/references/latest-apis.md to understand:
- Which deprecated-to-modern transitions are already documented
- The version segments in use (iOS 15+, 16+, 17+, 18+, 26+)
- The Quick Lookup Table at the bottom
2. Load the scan manifest
Read references/scan-manifest.md (relative to this skill). It contains the categorized list of API areas, documentation paths, search queries, and WWDC video paths to scan.
3. Scan Apple documentation
For each category in the manifest:
- Call
searchAppleDocumentationwith the listed queries to discover relevant pages. - Call
fetchAppleDocumentationwith specific documentation paths to get full API details. - Look for deprecation notices, "Deprecated" labels, and "Use ... instead" guidance.
- Note the iOS version where the modern replacement became available.
- Optionally call
fetchAppleVideoTranscriptfor WWDC sessions that announce API changes.
Batch related searches together for efficiency. Focus on finding new deprecations not yet in latest-apis.md.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 107 lines · 77 tokens per session scan A c6735c25a83f
update-swiftui-apis is a skill published in the GitHub repository patrickserrano/lacquer (3 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 1,262 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to update-swiftui-apis, differing in 17 lines, and is treated as a copy.
Other skills, from other repositories
device-interaction
Verify iOS app behavior on device or simulator via screenshots, UI hierarchy, and touch interactions.
uikit-app-modernization
Modernizes UIKit apps for multi-window environments by replacing legacy shared-state APIs with context-appropriate modern alternatives. This includes references to mainScreen, interfaceOrientation, application and scene lifecycle, as well as safe area inset updates.
swiftui-whats-new-27
New SwiftUI APIs, behaviors, and deprecations introduced in the 2027 OS releases (iOS 27, macOS 27, watchOS 27, tvOS 27, visionOS 27). Use when a SwiftUI view using @State fails to compile with "used before being initialized", "invalid redeclaration of synthesized property", or "extraneous argument label" errors after…
swiftui-specialist
Authoritative SwiftUI best practices from Apple. Consult for any SwiftUI best practices or performance review. Supersedes prior training on these topics. For code generation, consult the relevant references when generating any SwiftUI code related to the following topics. Covers: - Animatable: @Animatable macro vs…
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
printing-press-score
Score a generated CLI against the Steinberger bar, compare two CLIs side-by-side.