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-runtime-lifecyclegit 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-runtime-lifecycle)<a href="https://agentmods.dev/skills/jakubmikolajek/codex-skills-collection/tauri-runtime-lifecycle"><img src="https://agentmods.dev/badge/skills/jakubmikolajek/codex-skills-collection/tauri-runtime-lifecycle/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-runtime-lifecycle"><img src="https://agentmods.dev/badge/skills/jakubmikolajek/codex-skills-collection/tauri-runtime-lifecycle.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.00044 | $0.00685 |
| Opus 5 | $0.00022 | $0.00342 |
| Sonnet 5 | $0.00009 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
tauri-runtime-lifecycle 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 10d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tauri Runtime Lifecycle
Use this skill when task complexity centers on runtime state, long-lived managers, and lifecycle correctness.
When to Use
- Adding/refactoring Tauri
State<>managers and shared runtime services - Implementing startup/shutdown logic, background workers, or supervisor loops
- Fixing leaks/zombie processes/listener buildup across app relaunches
- Coordinating command handlers with long-running tasks and cancellation flows
When NOT to Use
- Task is only command DTO boundary work (use
tauri-command-contract) - Task is only window/titlebar UX behavior (use
tauri-window-shell) - Task is purely static config/build packaging with no runtime manager logic
Delivery Workflow
Tauri runtime lifecycle progress:
- [ ] Step 1: Map runtime owners (State, managers, workers, event channels)
- [ ] Step 2: Define startup, ready, degraded, shutdown states explicitly
- [ ] Step 3: Implement cancellation and cleanup paths for long-running tasks
- [ ] Step 4: Verify command interactions with manager lifecycle
- [ ] Step 5: Add lifecycle smoke tests and shutdown/restart verification
Core Rules
- Each long-lived service must have explicit owner, start path, and stop path.
- Commands that trigger background work must expose cancellable or idempotent behavior.
- Keep synchronization explicit; avoid ad-hoc shared mutable state across unrelated managers.
- Ensure listeners/subscriptions are detached on shutdown/unmount.
- Prefer structured events and state snapshots over implicit flags scattered in code.
Runtime Safety Checklist
- [ ] Manager init happens once per app lifecycle (or intentionally per workspace/session)
- [ ] Cancellation path exists for each long-running task
- [ ] Shutdown closes resources (PTY/processes/watchers/channels)
- [ ] Command handlers validate manager readiness before use
- [ ] Restart/relaunch path does not duplicate workers/listeners
Test Matrix (Lifecycle)
- startup -> ready: manager initialization and registration
- ready -> running task -> cancel: cancellation semantics and resource cleanup
- runtime error path: degraded/recoverable behavior
- shutdown: all workers/listeners/resources released
- relaunch: no duplicated background tasks from prior session
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.
- 10d ago First seen · 76 lines · 44 tokens per session scan A e76c450c3146
tauri-runtime-lifecycle is a skill published in the GitHub repository JakubMikolajek/codex-skills-collection (5 stars, last pushed 5d ago), licensed MIT. It adds 44 tokens to every session and 685 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-08-31.
Other skills, from other repositories
azure-eventhub-rust
Azure Event Hubs library for Rust. Send and receive events for streaming data ingestion and batch processing. Triggers: "event hubs rust", "ProducerClient rust", "ConsumerClient rust", "send event rust", "streaming rust", "eventhub rust".
rust-engineer
Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or…
azure-eventhub-rust
Client library for Azure Event Hubs — big data streaming platform and event ingestion service.
cloudflare-workers-multi-lang
Multi-language Workers development with Rust, Python, and WebAssembly. Use when building Workers in languages other than JavaScript/TypeScript, or when integrating WASM modules for performance-critical code.
actix-web
Actix Web is a powerful, high-performance web framework for Rust. It provides async handlers, type-safe extractors, middleware, and integrates with the Rust ecosystem for building fast, reliable, and memory-safe web services.
axum
You are an expert in Axum, the web framework built on top of Tokio and Tower by the Tokio team. You help developers build high-performance, type-safe APIs and web services using Axum's extractor-based handler system, middleware via Tower layers, WebSocket support, and compile-time route validation — achieving C-level…