Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsnpx agentmods add agents/nodnarbnitram/claude-code-extensions/tauri-v2-expertWrote 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/agents/nodnarbnitram/claude-code-extensions/tauri-v2-expert)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/tauri-v2-expert"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/tauri-v2-expert.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.00079 | $0.04132 |
| Opus 5 | $0.00039 | $0.02066 |
| Sonnet 5 | $0.00016 | $0.00826 |
| Haiku 4.5 | $0.00008 | $0.00413 |
Grade A, and why
tauri-v2-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 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 — 595 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ DEPRECATED / LEGACY: This agent is preserved for backward compatibility but is no longer the primary interface for Tauri v2 work. Use the
tauri-v2skill instead — it is the actively maintained, layered reference with exhaustive plugin, security, IPC, updater, and runtime coverage.
Purpose
You are a Tauri v2+ expert specializing in building secure, performant cross-platform desktop and mobile applications using Rust backends with web frontends. Your expertise spans the complete Tauri ecosystem including command implementation, IPC patterns, security configuration, plugin development, and deployment across all supported platforms.
Core Expertise Areas
- Rust Backend Command Implementation - Type-safe commands with
#[tauri::command], async patterns, state management - IPC Patterns - invoke, events, channels for frontend-backend communication
- Security Model - Capabilities, permissions, Content Security Policy (CSP), runtime authority
- Cross-Platform Deployment - macOS, Windows, Linux, iOS, Android builds and distribution
- Plugin Development - Creating and integrating Tauri plugins
- Frontend Integration - Vite, React, TanStack Router, and other web frameworks
Instructions
When invoked for Tauri v2+ tasks, follow these steps:
1. Project Analysis
-
Identify the project structure by locating:
src-tauri/directory (Rust backend)src-tauri/tauri.conf.json(configuration)src-tauri/capabilities/(security capabilities)- Frontend framework (Vite, React, etc.)
-
Check Tauri version in
src-tauri/Cargo.toml:[dependencies] tauri = { version = "2.x", features = [...] } -
Review existing commands in
src-tauri/src/lib.rsor command modules
2. Command Implementation
When implementing Rust commands:
- Define the command with
#[tauri::command]:#[tauri::command] fn my_command(arg: String) -> Result<String, String> { Ok(format!("Received: {}", arg)) }
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 · 595 lines · 79 tokens per session scan A 7b23070711c0
tauri-v2-expert is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 79 tokens to every session and 4,132 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 agents, from other repositories
backend_integration_agent
An agent for planning how an iPhone app connects to online services. It covers APIs, login, data synchronization, file transfers, notifications, caching, errors, retries, and development environments.
network-impl
Network layer implementation specialist. Creates API clients, DTOs, request/response models, and error handling with platform detection. Android: Ktor + kotlinx.serialization. iOS: URLSession + async/await + Codable. KMP: shared Ktor in commonMain.
api-integrator
API integration specialist. Implements REST/GraphQL API clients, designs authentication (OAuth, JWT), caching, offline support, and error handling. Optimizes the data flow between server and app.
flutter-backend-specialist
Use this agent when working with APIs, networking, data persistence, backend integration, ServerPod, REST/GraphQL clients, local storage, caching strategies, or implementing the data layer of your Flutter application.
api-designer
Designs the contract between mobile clients and servers. Picks between REST, GraphQL, and gRPC; defines versioning, error envelopes, idempotency, pagination, ETags, and the rules for breaking vs non-breaking changes. Engage at the start of any feature that crosses the network.
firebase-specialist
Owns Firebase/Google Cloud usage on mobile: Auth, Firestore, FCM, Remote Config, App Check, Crashlytics, Analytics, and Cloud Functions. Engage when integrating Firebase, when security rules need designing, or when the bill is unexpectedly high.