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 swiftui-liquid-glassgit 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/swiftui-liquid-glass)<a href="https://agentmods.dev/skills/patrickserrano/lacquer/swiftui-liquid-glass"><img src="https://agentmods.dev/badge/skills/patrickserrano/lacquer/swiftui-liquid-glass/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/patrickserrano/lacquer/swiftui-liquid-glass"><img src="https://agentmods.dev/badge/skills/patrickserrano/lacquer/swiftui-liquid-glass.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.00050 | $0.01540 |
| Opus 5 | $0.00025 | $0.00770 |
| Sonnet 5 | $0.00010 | $0.00308 |
| Haiku 4.5 | $0.00005 | $0.00154 |
Grade A, and why
swiftui-liquid-glass 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 5d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SwiftUI Liquid Glass
Overview
Liquid Glass is a dynamic material in iOS 26+ that combines optical glass properties with fluidity. It blurs content, reflects surrounding color and light, and reacts to touch interactions in real time.
Workflow Decision Tree
1) Review an existing feature
- Inspect where Liquid Glass should/shouldn't be used
- Verify correct modifier order, shape usage, container placement
- Check for iOS 26+ availability handling and fallbacks
2) Improve a feature using Liquid Glass
- Identify target components (surfaces, chips, buttons, cards)
- Refactor to use
GlassEffectContainerfor multiple glass elements - Add interactive glass only for tappable/focusable elements
3) Implement a new feature using Liquid Glass
- Design glass surfaces and interactions first (shape, prominence, grouping)
- Add glass modifiers after layout/appearance modifiers
- Add morphing transitions only when view hierarchy changes with animation
Core Guidelines
- Prefer native Liquid Glass APIs over custom blurs
- Use
GlassEffectContainerwhen multiple glass elements coexist - Apply
.glassEffect(...)after layout and visual modifiers - Use
.interactive()for elements that respond to touch/pointer - Keep shapes consistent across related elements
- Gate with
#available(iOS 26, *)and provide non-glass fallback
Review Checklist
- Availability:
#available(iOS 26, *)present with fallback UI - Composition: Multiple glass views wrapped in
GlassEffectContainer - Modifier order:
glassEffectapplied after layout/appearance modifiers - Interactivity:
interactive()only where user interaction exists - Transitions:
glassEffectIDused with@Namespacefor morphing - Consistency: Shapes, tinting, and spacing align across feature
Implementation Checklist
- Define target elements and desired glass prominence
- Wrap grouped glass elements in
GlassEffectContainerwith spacing - Use
.glassEffect(.regular.tint(...).interactive(), in: .rect(cornerRadius: ...))as needed - Use
.buttonStyle(.glass)/.buttonStyle(.glassProminent)for actions - Add morphing transitions with
glassEffectIDwhen hierarchy changes - Provide fallback materials for earlier iOS versions
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.
- 5d ago First seen · 181 lines · 50 tokens per session scan A bb1e2acb082d
swiftui-liquid-glass is a skill published in the GitHub repository patrickserrano/lacquer (3 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 1,540 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-09-03.
Other skills, from other repositories
expo-config-plugin
Writing Expo config plugins, withInfoPlist, withAndroidManifest, withDangerousMod, mod compose, plugin testing, and registration in app.config.ts. Triggers on config plugin, with-plugin, withInfoPlist, withAndroidManifest, withDangerousMod, withEntitlementsPlist, withGradleProperties, mod, native config, expo plugin…
expo-router
File-based routing with Expo Router, dynamic routes, layout hierarchy, deep linking, and navigation patterns. Triggers on expo-router, file-based routing, app dizini, layout.tsx, [id].tsx, deep linking, expo-linking, tab navigation, stack navigation, drawer, prefetch, parallel routes, redirects, navigation, useRouter…
miniapp-center-hub-refactor
Refactor a growing WeChat Mini Program whose top-level navigation has become scattered across tabs such as home, profile, inbox, integrations, or settings into a clearer hub or center structure. Use when Codex needs to regroup top-level tabs, separate high-frequency action flows from low-frequency settings, define…
miniapp-official-scaffold-alignment
Validate or design a WeChat Mini Program scaffold, repository layout, or TypeScript setup against official platform rules. Use when Codex needs to review project.config.json, app.json, miniprogramRoot, page or component file sets, or the initial repo skeleton before feature work begins.
design-system
Frontend design conventions for {{ projectname }} -- layout hierarchy, spacing, typography, anti-slop rules. Auto-activates when creating or modifying templates, CSS, or frontend components.
expo-prebuild
Managed-to-bare transition with Expo prebuild, the ios/android directories, .easignore, native-upgrade discipline, and custom-mod application order. Triggers on expo prebuild, prebuild, managed to bare, bare workflow, native upgrade, ios android directory, easignore, prebuild cache, eject, sync native, native code…