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.
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 agentmods add skills/robinebers/openusage/liquid-glassnpx skills add robinebers/openusage --skill liquid-glassgit 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/liquid-glass)<a href="https://agentmods.dev/skills/robinebers/openusage/liquid-glass"><img src="https://agentmods.dev/badge/skills/robinebers/openusage/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.00074 | $0.01868 |
| Opus 5 | $0.00037 | $0.00934 |
| Sonnet 5 | $0.00015 | $0.00374 |
| Haiku 4.5 | $0.00007 | $0.00187 |
Grade A, and why
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 6d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- liquid-glass — 94% identical, 2 lines differ
- macos-liquid-glass — 89% identical, 14 lines differ
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
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.
- 6d ago First seen · 171 lines · 74 tokens per session scan A 45657c387be6
liquid-glass is a skill published in the GitHub repository robinebers/openusage (4,021 stars, last pushed today), licensed MIT. It adds 74 tokens to every session and 1,868 once invoked, about $0.0004 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
react-native-expert
Senior React Native and Expo engineer for building production-ready cross-platform mobile apps. Use when building React Native components, implementing navigation with Expo Router, optimizing list and scroll performance, working with animations via Reanimated, handling platform-specific code (iOS/Android), integrating…
godot-adapt-desktop-to-mobile
Expert patterns for porting desktop games to mobile including touch control schemes (virtual joystick, gesture detection), UI scaling for small screens, performance optimization for mobile GPUs, battery life management, and platform-specific features. Use when creating mobile ports or cross-platform mobile builds.…
godot-prompter-mobile-development
Imported GodotPrompter guidance for mobile-development workflows in game development projects.
godot-platform-mobile
Expert blueprint for mobile platforms (Android/iOS) covering touch controls, virtual joysticks, responsive UI, safe areas (notches), battery optimization, and app store guidelines. Use when targeting mobile releases or implementing touch input. Keywords mobile, Android, iOS, touch, InputEventScreenTouch, virtual…
hig-technologies
Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.
debug-live
Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…