robinebers/openusage is a native macOS menu-bar application that tracks usage of AI coding subscriptions, including limits, credits, and spending. Developers use it to monitor plans from services such as Claude, Codex, Cursor, and Copilot, while the catalogue entries support related workflows.
Borrowing it
Nothing to install: this file belongs to robinebers/openusage. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/robinebers/openusage/main/.agents/skills/macos-liquid-glass/SKILL.mdgit clone --depth 1 https://github.com/robinebers/openusageWrote 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/robinebers/openusage/macos-liquid-glass)<a href="https://agentmods.dev/skills/robinebers/openusage/macos-liquid-glass"><img src="https://agentmods.dev/badge/skills/robinebers/openusage/macos-liquid-glass.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.00033 | $0.01839 |
| Opus 5 | $0.00016 | $0.00920 |
| Sonnet 5 | $0.00007 | $0.00368 |
| Haiku 4.5 | $0.00003 | $0.00184 |
Grade A, and why
macos-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 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.
This is a copy
89% identical to liquid-glass — 14 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Liquid Glass
Overview
Use this skill to bring a macOS SwiftUI app into the modern macOS design system with the least custom chrome possible. Start with standard app structure, toolbars, search placement, sheets, and controls, then add custom Liquid Glass only where the app needs a distinctive surface.
Prefer system-provided glass and adaptive materials over bespoke blur, opaque backgrounds, or custom toolbar/sidebar skins. Audit existing UI for extra fills, scrims, and clipping before adding more effects.
Workflow
- Read the relevant scene or root view and identify the structural pattern:
NavigationSplitView,TabView, sheet presentation, detail/inspector layout, toolbar, or custom floating controls. - Remove custom backgrounds or darkening layers behind system sheets, sidebars, and toolbars unless the product explicitly needs them. These can obscure Liquid Glass and interfere with the automatic scroll-edge effect.
- Update standard SwiftUI structure and controls first.
- Add custom
glassEffectsurfaces only for app-specific UI that standard controls do not cover. - Validate that glass grouping, transitions, icon treatment, and foreground activation are visually coherent and still usable with pointer and keyboard.
- If the UI change also affects launch behavior for a SwiftPM GUI app, use
macos-build-run-debugso the app runs as a foreground.appbundle rather than as a raw executable.
App Structure
- Prefer
NavigationSplitViewfor hierarchy-driven macOS layouts. Let the sidebar use the system Liquid Glass material instead of painting over it. - For hero artwork or large media adjacent to a floating sidebar, use
backgroundExtensionEffectso the visual can extend beyond the safe area without clipping the subject. - Keep inspectors visually associated with the current selection and avoid giving them a heavier custom background than the content they inspect.
- If the app uses tabs, keep
TabViewfor persistent top-level sections and preserve each tab's local navigation state. - Do not force iPhone-only tab bar minimize/accessory behavior onto a Mac app. On macOS, prefer a conventional top toolbar and native tab/search placement.
- If a sheet already uses
presentationBackgroundpurely to imitate frosted material, consider removing it and letting the system's new material render. - For sheet transitions that should visually originate from a toolbar button, make the presenting item the source of a navigation zoom transition and mark the sheet content as the destination.
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 · 171 lines · 33 tokens per session scan A 0126ff3bf600
macos-liquid-glass is a skill published in the GitHub repository robinebers/openusage (4,061 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 1,839 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to liquid-glass, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
tailwind-design-system
Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
motion-graphics
Use when the user wants a short, design-led motion graphic where motion is the message: kinetic typography, stat or number count-up, chart/data-viz hit, logo sting, brand lockup, lower-third, callout, social overlay, animated headline/tweet/news item, motion poster, or quick captured-page highlight. Usually under 10s…
visual-style
Create, extract, and apply portable visual design systems via visual-style.md files. Use when: (1) Creating a visual-style.md design system from scratch, (2) Extracting a visual style from a website URL, video, or PDF brand guide, (3) Applying a visual style to HeyGen videos, HTML slides, Figma, or paper.design, (4)…
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
figma-connect
Figma-to-code bridge combining Figma MCP server tools with the Code Connect CLI for end-to-end design implementation workflows. Use this skill when implementing UI components from Figma design URLs, publishing Code Connect mappings to Figma Dev Mode, extracting design tokens from Figma variables, setting up Figma Code…