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 JakubMikolajek/codex-skills-collection --skill tauri-window-shellgit clone --depth 1 https://github.com/JakubMikolajek/codex-skills-collectionWrote 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/jakubmikolajek/codex-skills-collection/tauri-window-shell)<a href="https://agentmods.dev/skills/jakubmikolajek/codex-skills-collection/tauri-window-shell"><img src="https://agentmods.dev/badge/skills/jakubmikolajek/codex-skills-collection/tauri-window-shell/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/jakubmikolajek/codex-skills-collection/tauri-window-shell"><img src="https://agentmods.dev/badge/skills/jakubmikolajek/codex-skills-collection/tauri-window-shell.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.00045 | $0.00899 |
| Opus 5 | $0.00023 | $0.00449 |
| Sonnet 5 | $0.00009 | $0.00180 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
tauri-window-shell 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 9d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tauri Window Shell
Use this skill for desktop-shell behavior where React UI controls a native Tauri window.
When to Use
- Custom titlebar implementation (frameless window, drag regions, native control buttons)
- Window controls (
minimize,toggleMaximize,close, fullscreen) - Drag/double-click behaviors in top bar (
startDragging, maximize on titlebar double-click) - Startup bounds/restore behavior and window state sync with frontend UI
- Regressions where web UI looks correct but native window behavior is broken
When NOT to Use
- Pure web React work with no Tauri runtime
- Rust-side command/business logic with no window-shell behavior (use
rust) - General CSS/layout issues unrelated to native window integration
Delivery Workflow
Tauri window shell progress:
- [ ] Step 1: Confirm runtime and API version (`@tauri-apps/api` v1 vs v2)
- [ ] Step 2: Map titlebar interaction zones (drag zone vs interactive controls)
- [ ] Step 3: Implement window API calls and event wiring
- [ ] Step 4: Verify startup bounds/maximize/minimize/close behavior
- [ ] Step 5: Re-test edge cases (double-click, resize, multi-monitor, relaunch)
General References (Tauri v2)
Read references/tauri-v2.md when:
- confirming current
@tauri-apps/apiwindow APIs - wiring listeners for window state synchronization
- validating shell behavior and common desktop edge cases
Core Rules
- Keep a single window adapter module for all
@tauri-apps/api/windowcalls; avoid scattering raw API calls across components. - Never attach drag behavior to interactive controls (search input, tabs, buttons); only dedicated drag regions.
- Handle titlebar double-click intentionally: either maximize/restore or disabled by product decision.
- Keep native-window state and UI state synchronized after every action (maximize icon, disabled states, menu affordances).
- Test behavior in real desktop runtime, not only browser dev mode.
Interaction Zone Contract
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.
- 9d ago First seen · 92 lines · 45 tokens per session scan A ad403d1906a5
tauri-window-shell is a skill published in the GitHub repository JakubMikolajek/codex-skills-collection (5 stars, last pushed 7d ago), licensed MIT. It adds 45 tokens to every session and 899 once invoked, about $0.0002 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
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
fuzzy-ranking
Rank fuzzy matches with rankItem, filter with RankingInfo.passed, compare saved ranking metadata with compareItems, and configure rankings, thresholds, accessors, min/max bounds, or diacritics. Load for @tanstack/match-sorter-utils itself or fuzzy Table filterMeta wiring.
api-not-found
Diagnose missing TanStack Table v9 exports, options, state slices, and instance methods. Load before inventing an API when code sees a type error, undefined feature method, absent object key, adapter mismatch, or v8-shaped example.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.