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 fellipeutaka/leon --skill taurigit clone --depth 1 https://github.com/fellipeutaka/leonWrote 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/fellipeutaka/leon/tauri)<a href="https://agentmods.dev/skills/fellipeutaka/leon/tauri"><img src="https://agentmods.dev/badge/skills/fellipeutaka/leon/tauri.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.00086 | $0.01115 |
| Opus 5 | $0.00043 | $0.00558 |
| Sonnet 5 | $0.00017 | $0.00223 |
| Haiku 4.5 | $0.00009 | $0.00112 |
Grade A, and why
tauri 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 3d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tauri v2 Development Skill
Build cross-platform desktop and mobile apps with web frontends and Rust backends using Tauri v2.
Core Principles
- Architecture: Use Rust for the backend (performance, native APIs) and any web framework for the frontend (UI, routing).
- Communication: Use Tauri's IPC (
invoke,events,channels) to bridge the Rust backend and the web frontend. - Security-First: Everything is denied by default. Explicitly configure permissions in
src-tauri/capabilities/to allow frontend access to backend commands and plugins. - Cross-Platform: Write once, compile to Windows, macOS, Linux, Android, and iOS. Use
lib.rsfor shared logic.
Quick Setup Checklist
Before making changes to a Tauri project, verify:
src-tauri/tauri.conf.jsonhasbuild.devUrlandbuild.frontendDistconfigured.src-tauri/capabilities/default.jsonexists and includes necessary permissions.- All custom Rust commands are registered in
tauri::generate_handler![]withinlib.rsormain.rs. lib.rscontains shared code, essential for mobile builds.
Primary Workflows
Creating and Using Commands
- Define the command in Rust with
#[tauri::command]:// src-tauri/src/lib.rs #[tauri::command] fn greet(name: String) -> Result<String, String> { Ok(format!("Hello, {}!", name)) } - Register the command in
tauri::Builder:tauri::Builder::default() .invoke_handler(tauri::generate_handler![greet]) // ... - Invoke the command from the frontend:
import { invoke } from '@tauri-apps/api/core'; const response = await invoke<string>('greet', { name: 'World' });
For more detailed IPC patterns (async, error handling, events, channels), see ipc.md.
Managing Application State
- Define state struct with thread-safe types (e.g.,
Mutex):use std::sync::Mutex; struct AppState { counter: Mutex<u32> } - Register state in the builder:
tauri::Builder::default() .setup(|app| { app.manage(AppState { counter: Mutex::new(0) }); Ok(()) }) - Access state in commands:
#[tauri::command] fn increment(state: tauri::State<'_, AppState>) -> Result<u32, String> { let mut count = state.counter.lock().map_err(|e| e.to_string())?; *count += 1; Ok(*count) }
What ships with it
5 files 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.
- 3d ago First seen · 101 lines · 86 tokens per session scan A c00aa76a5ac9
tauri is a skill published in the GitHub repository fellipeutaka/leon (5 stars, last pushed 3d ago), licensed MIT. It adds 86 tokens to every session and 1,115 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-09-03.
Other skills, from other repositories
build-native
Build connectnoritobridge native .so files from Rust source. Use when user says "build native", "build .so", "rebuild native libs", "update native bridge", or "cargo ndk build".
tauri-expert
Expert skill for Tauri (v2) development, Rust backend, IPC, and security / Panduan ahli untuk pengembangan Tauri v2, Rust backend, IPC, dan keamanan.
tauri-v2
Tauri v2 cross-platform app development with Rust backend. Use when configuring tauri.conf.json, implementing Rust commands (#[tauri::command]), setting up IPC patterns (invoke, emit, channels), configuring permissions/capabilities, troubleshooting build issues, or deploying desktop/mobile apps. Triggers on Tauri…
rust-tauri-apps
Implicit Rust Tauri v2 skill. Use for Tauri apps, Rust commands, invoke contracts, app state, plugins, capabilities and permissions, secure IPC, filesystem and shell access, sidecars, updater, bundling, desktop and mobile distribution, and Rust frontend bridge design.
uniffi-bindgen-react-native
A development guide for uniffi-bindgen-react-native, a tool for connecting Rust code to React Native apps. It includes its underlying model, comparisons, a quick reference, and a Rust example.
tauri-v2
Tauri v2+ cross-platform app development with Rust backend. Use when configuring tauri.conf.json, implementing Rust commands (#[tauri::command]), setting up IPC patterns (invoke, emit, channels), configuring permissions/capabilities, troubleshooting build issues, or deploying desktop/mobile apps. Triggers on Tauri…