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 roedyrustam/vibes-plug --skill tauri-expertgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/tauri-expert)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/tauri-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/tauri-expert.svg" alt="Measured on agentmods" 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.00043 | $0.01409 |
| Opus 5 | $0.00022 | $0.00705 |
| Sonnet 5 | $0.00009 | $0.00282 |
| Haiku 4.5 | $0.00004 | $0.00141 |
Grade A, and why
tauri-expert 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 4d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tauri Expert
English
Orchestration & Integration
Connects and orchestrates with relevant domain skills like brainstorming, zero-to-prod-orchestrator, and project-context-mapper to ensure cohesive execution.
Description
This skill provides best practice guidance for building cross-platform desktop and mobile applications using Tauri (specifically Tauri v2). It covers frontend integration with the Rust backend, Inter-Process Communication (IPC), state management, and security.
Instructions & Best Practices
1. Architecture & IPC (Inter-Process Communication)
- Use
tauri::commandto define Rust functions callable from the frontend. - Invoke Rust functions from the frontend using
@tauri-apps/api/core(invoke). - Utilize Tauri's event system (
emitfrom Rust,listenon frontend) for real-time or async updates. - Keep heavy processing and filesystem access in Rust (backend), while the frontend focuses purely on UI.
2. State Management (Rust Backend)
- Use
tauri::Stateto store and manage global state in the Rust backend. - Use
std::sync::Mutexortokio::sync::Mutex(if async) for mutable state. - Initialize managed state during application setup:
tauri::Builder::default().manage(MyState::default()).
3. Security & Capabilities
- Enforce strict context isolation.
- In Tauri v2, use the Capabilities system to restrict API access per window or plugin.
- Never expose dangerous filesystem, shell, or network APIs globally. Only grant allowlist access to specific, required paths or commands.
4. Performance & Concurrency
- Use
async fnfortauri::commandwhen handling heavy I/O to avoid blocking the main thread. - Use
serde(Serialize,Deserialize) efficiently for data structures sent between Rust and the frontend.
5. Plugin Management (Tauri v2)
- Use official Tauri plugins (e.g.,
tauri-plugin-fs,tauri-plugin-store,tauri-plugin-dialog) instead of writing custom I/O modules when available. - Initialize plugins in
main.rsorlib.rs:app.plugin(tauri_plugin_dialog::init()).
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.
- 4d ago First seen · 104 lines · 43 tokens per session scan A 719d0d3b68d7
tauri-expert is a skill published in the GitHub repository roedyrustam/vibes-plug (49 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,409 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
dart-flutter-patterns
Production-ready Dart and Flutter patterns covering null safety, immutable state, async composition, widget architecture, popular state management frameworks (BLoC, Riverpod, Provider), GoRouter navigation, Dio networking, Freezed code generation, and clean architecture.
android-clean-architecture
Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns.
android-clean-architecture
Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns.
compose-multiplatform-patterns
Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.
swiftui-patterns
SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS/macOS UI best practices.
android-jetpack-compose-expert
Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3.