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-window-management/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-window-management)<a href="https://agentmods.dev/skills/robinebers/openusage/macos-window-management"><img src="https://agentmods.dev/badge/skills/robinebers/openusage/macos-window-management/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/robinebers/openusage/macos-window-management"><img src="https://agentmods.dev/badge/skills/robinebers/openusage/macos-window-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.01824 |
| Opus 5.5 | $0.00014 | $0.00730 |
| Sonnet 5.5 | $0.00007 | $0.00365 |
| Haiku 4.5 | $0.00004 | $0.00182 |
Grade A, and why
macos-window-management 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 2mo 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
1 near-identical copy found in the catalogue:
- window-management — 100% 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.
Window Management
Overview
Use this skill to tailor each SwiftUI window to its job. Start by identifying
which scene owns the window (Window, WindowGroup, or a dedicated utility
scene), then customize the toolbar/title area, background material, resize and
restoration behavior, and initial or zoomed placement.
Prefer scene and window modifiers over ad hoc AppKit bridges when SwiftUI offers the behavior directly. Keep each window purpose-built: a main browser window, an About window, and a media player window usually want different chrome, resizability, restoration, and placement rules.
These APIs are macOS 15+ SwiftUI window/scene customizations. For older deployment targets, expect to use more AppKit bridging or availability guards.
Workflow
- Inspect the relevant scene declaration and classify the window role: main app navigation, inspector/detail utility, About/support window, media playback window, welcome window, or a borderless custom surface.
- Adjust toolbar and title presentation to match the content.
- If the toolbar background or entire toolbar is hidden, make sure the window still has a usable drag region.
- Refine window behavior for that role: minimize availability, restoration, resize expectations, and whether the window should appear at launch.
- Set default placement for newly opened windows and ideal placement for zoom behavior when content and display size matter.
- Build and launch the app with
macos-build-run-debugto verify the result in a real foreground.appbundle. - If SwiftUI scene/window modifiers are not enough, switch to
macos-appkit-interopfor a narrowNSWindowbridge rather than spreading AppKit through the view tree.
Toolbar And Title
- Use
.toolbar(removing: .title)when the window title should stay associated with the window for accessibility and menus, but not be visibly drawn in the title bar. - Use
.toolbarBackgroundVisibility(.hidden, for: .windowToolbar)when large media or hero content should visually extend to the top edge of the window. - If the window still needs close/minimize/full-screen controls, remove only the
title and toolbar background. If the toolbar should disappear entirely, use
.toolbarVisibility(.hidden, for: .windowToolbar)instead. - Remove custom toolbar backgrounds and manually painted titlebar fills before layering new SwiftUI toolbar APIs on top.
- Keep the window's logical title meaningful even if hidden; the system can still use it for accessibility and menu items. These are visual changes only.
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.
- 2mo ago First seen · 171 lines · 36 tokens per session scan A 548167ec90f8
macos-window-management is a skill published in the GitHub repository robinebers/openusage (4,556 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,824 once invoked, about $0.0001 per session on Opus 5.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.
macos-window-management compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| macos-window-managementrobinebers/openusage | Skill | 4.6k | yesterday | MIT | A | 36 | Claude Code, Codex |
| tailwind-design-systemcalesthio/OpenMontage | Skill | 77k | 3d ago | AGPL-3.0 | A | 42 | Claude Code, Codex |
| motion-graphicscalesthio/OpenMontage | Skill | 77k | 3d ago | AGPL-3.0 | A | 187 | Claude Code, Codex |
| visual-stylecalesthio/OpenMontage | Skill | 77k | 3d ago | AGPL-3.0 | A | 136 | Claude Code, Codex |
| vercel-composition-patternscalesthio/OpenMontage | Skill | 77k | 3d ago | AGPL-3.0 | A | 58 | Claude Code, Codex |
| web-design-guidelinescalesthio/OpenMontage | Skill | 77k | 3d ago | AGPL-3.0 | A | 44 | Claude Code, Codex |
| figma-connectanton-abyzov/vskill | Skill | 47 | 3d ago | MIT | A | 223 | Claude Code |