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 ios-secrets-setupgit 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/ios-secrets-setup)<a href="https://agentmods.dev/skills/patrickserrano/lacquer/ios-secrets-setup"><img src="https://agentmods.dev/badge/skills/patrickserrano/lacquer/ios-secrets-setup.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.00093 | $0.00687 |
| Opus 5 | $0.00046 | $0.00344 |
| Sonnet 5 | $0.00019 | $0.00137 |
| Haiku 4.5 | $0.00009 | $0.00069 |
Grade A, and why
ios-secrets-setup 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 3d 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.
What it actually says
iOS App-Runtime Secrets Setup
App-runtime keys (RevenueCat, Aptabase, …) live in a gitignored
Secrets.xcconfig, never in source or the committed project.yml. The
lacquer syncs a Secrets.xcconfig.example template into the component dir.
- Copy & ignore:
cp Secrets.xcconfig.example Secrets.xcconfig, fill in real values, and addSecrets.xcconfigto.gitignore. The example is committed; the real file never is. (The committedproject.ymlmust also stay key-free.) - Wire into the build (
project.yml): point the target's configs at the xcconfig and surface each key intoInfo.plist:targets: <App>: configFiles: Debug: Secrets.xcconfig Release: Secrets.xcconfig info: path: App/Info.plist properties: REVENUECAT_API_KEY: $(REVENUECAT_API_KEY) APTABASE_APP_KEY: $(APTABASE_APP_KEY) - Read at runtime from the Info dictionary — fail loud if a required key
is blank rather than shipping a broken SDK init:
enum Secrets { static func required(_ key: String) -> String { guard let v = Bundle.main.object(forInfoDictionaryKey: key) as? String, !v.isEmpty else { fatalError("Missing \(key) — copy Secrets.xcconfig.example to Secrets.xcconfig and fill it in") } return v } static var revenueCatAPIKey: String { required("REVENUECAT_API_KEY") } static var aptabaseAppKey: String { required("APTABASE_APP_KEY") } }
Secrets.xcconfig values are build-time — they are baked into the
binary, so treat them as obfuscated, not secret. A truly sensitive secret
belongs on a server, never in the app.
RevenueCat ships two different keys — do not confuse them. The
REVENUECAT_API_KEYabove is the public SDK key (appl_…), safe to compile into the app. RevenueCat's REST API uses a separate secret key (sk_…) that grants full account access — it must never go inSecrets.xcconfigor the binary. That's a CI/server secret (REVENUECAT_REST_API_KEY), set viagh secret setper the project'sCLAUDE.mdSecrets section.
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.
- 3d ago First seen · 62 lines · 93 tokens per session scan A 2ba77e3421d0
ios-secrets-setup is a skill published in the GitHub repository patrickserrano/lacquer (3 stars, last pushed yesterday), licensed MIT. It adds 93 tokens to every session and 687 once invoked, about $0.0005 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-09-03.
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.