Agent skill

Tauri Security Review

by mukiwu in mukiwu/tempo-term

Expert workflow for reviewing Tauri 2 desktop app security. An agent skill from mukiwu/tempo-term.

Apache-2.0Auto-check: notesSecurity

Install Tauri Security Review

skills CLI
$ npx skills add mukiwu/tempo-term --skill tauri-security-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukiwu/tempo-term tauri-security-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukiwu/tempo-term.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/tauri-security-review .claude/skills/tauri-security-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tauri-security-review
GitHub stars
229
Token cost
~2.8k tokens
SKILL.md length
344 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
Apache-2.0

At a glance

Expert workflow for reviewing Tauri 2 desktop app security. An agent skill from mukiwu/tempo-term.

  • Tasks that involve Security review
  • SKILL.md covers When to Use, Core Principle: Frontend Is…, Checklist by File Type and Common Tauri 2 Security Bug…, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Tauri Security Review is an agent skill from mukiwu/tempo-term. Expert workflow for reviewing Tauri 2 desktop app security. Covers capabilities/permissions least-privilege, IPC trust boundary, command input validation, CSP, scope restriction, isolation pattern, and frontend-side hygiene.

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Security, covering Security review. It works with Tauri. The repository describes itself as: AI-powered terminal, editor and file explorer. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Security review

Example prompts

  • “/tauri-security-review”

What it can do on your machine

Read from SKILL.md and the folder at commit 6750c17. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are rust and json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • v2.tauri.app

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tauri Security Review loads about 2.8k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 344 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:38
    s added for sensitive subpaths (secrets, .env)

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mukiwu/tempo-term at commit 6750c17, republished under its Apache-2.0 licence (© mukiwu). 344 words, ~2,808 tokens.

Download SKILL.mdSave it as .claude/skills/tauri-security-review/SKILL.md (or your agent's skills folder).
name
tauri-security-review
description
Expert workflow for reviewing Tauri 2 desktop app security. Covers capabilities/permissions least-privilege, IPC trust boundary, command input validation, CSP, scope restriction, isolation pattern, and frontend-side hygiene.

Tauri 2 Security Review Skill

Expert workflow for reviewing Tauri 2 code with a focus on the IPC trust boundary, capability least-privilege, and command-level input validation.

When to Use

Invoke this skill (or the tauri-security-reviewer agent) when changes touch:

  • src-tauri/capabilities/*.json
  • src-tauri/permissions/*.toml
  • src-tauri/tauri.conf.json (security / app / bundle sections)
  • Any #[tauri::command] function
  • tauri::generate_handler! registration
  • tauri::Builder plugin registration
  • Frontend invoke() callers (especially passing user input)

Core Principle: Frontend Is Untrusted

The webview is part of the untrusted side of the trust boundary. Every command must validate every input as if it came from a remote attacker. A capability grants the ability to call a command — it does not validate the contents of the call.


Checklist by File Type

Capability Files (src-tauri/capabilities/*.json)
□ identifier is unique and descriptive
□ windows / webviews are explicitly listed (no broad globs unless justified)
□ permissions list is minimal — every entry has a justified use case
□ fs/shell/http permissions use scoped objects with allow path lists
□ allow paths use Tauri path vars ($APPDATA, etc.), not absolute paths
□ allow paths do NOT use ** wildcards
□ deny rules added for sensitive subpaths (secrets, .env)
□ platforms[] excludes platforms that don't need this capability
□ remote.urls (if present) is a specific allowlist, not "https://*"
□ local: false used when capability is for remote-only contexts
Custom Permission Files (src-tauri/permissions/*.toml)
□ identifier prefixed with intended namespace
□ commands.allow is the smallest set possible
□ scope.allow paths are specific
□ scope.deny added for any obvious dangerous subpath
□ description explains the security impact, not just the feature
tauri.conf.json
□ app.security.csp present and restrictive
   - default-src 'self'
   - no 'unsafe-inline' for script-src
   - no 'unsafe-eval' (except 'wasm-unsafe-eval' if WASM is used)
   - connect-src is a specific allowlist
□ app.security.devCsp present (or same as csp) — dev mode shouldn't relax everything
□ app.security.dangerousDisableAssetCspModification is NOT true
□ app.security.assetProtocol.scope is restrictive (not "**")
□ app.windows[].url is local (path) or trusted https — not http or untrusted host
□ build.devUrl is localhost only
□ identifier is reverse-DNS and matches the App Store record
□ plugins.shell.open is restrictive or absent
□ plugins.http.scope (if used) lists exact allowed origins
Rust Commands (#[tauri::command])
□ All path inputs validated:
   - canonicalize() to resolve symlinks
   - check that resolved path is inside an expected base dir
   - reject paths containing ".." segments or null bytes
□ Shell-bound inputs never concatenated — use std::process::Command with args[], not args.join(" ")
□ SQL inputs parameterized (never format!())
□ HTTP URLs validated to be in expected origin set
□ Input length bounded — no infinite-size strings/bytes accepted
□ Errors don't leak sensitive paths or stack traces (use a typed error enum that rewrites messages)
□ No unwrap()/expect() — they panic and crash the app
□ Async commands don't hold std::sync::Mutex across .await
□ No use of std::env::set_var (security side effects across threads)
invoke_handler! Registration
□ Single tauri::generate_handler![...] call (multiple calls silently overwrite)
□ All commands listed actually exist as #[tauri::command]
□ No leftover/dead command registrations exposing unused attack surface
Frontend Callers (invoke('cmd', { ... }))
□ User input never used as an `invoke` command name (must be a hardcoded string literal)
□ Argument types match the Rust signature exactly
□ Error from invoke is caught and shown safely (not innerHTML'd into DOM — XSS)

Common Tauri 2 Security Bug Patterns

Pattern 1: Over-Broad Capability Scope
json
// ❌ WRONG — frontend can read/write anywhere in $HOME
{
  "identifier": "main",
  "windows": ["main"],
  "permissions": [
    { "identifier": "fs:allow-write-text-file", "allow": [{ "path": "$HOME/**" }] }
  ]
}

// ✅ CORRECT — narrowly scoped to app data
{
  "identifier": "main",
  "windows": ["main"],
  "permissions": [
    { "identifier": "fs:allow-write-text-file", "allow": [{ "path": "$APPDATA/notes/*" }] }
  ]
}
Pattern 2: Path Traversal in Command
rust
// ❌ WRONG — frontend can escape with "../../../etc/passwd"
#[tauri::command]
async fn read_note(name: String, app: AppHandle) -> Result<String, NoteError> {
    let dir = app.path().app_data_dir()?;
    let path = dir.join(&name);
    Ok(tokio::fs::read_to_string(&path).await?)
}

// ✅ CORRECT — canonicalize and verify containment
#[tauri::command]
async fn read_note(name: String, app: AppHandle) -> Result<String, NoteError> {
    let dir = app.path().app_data_dir()?.canonicalize()?;
    let path = dir.join(&name).canonicalize()?;
    if !path.starts_with(&dir) {
        return Err(NoteError::InvalidPath);
    }
    Ok(tokio::fs::read_to_string(&path).await?)
}
Pattern 3: Shell Injection via String Concat
rust
// ❌ WRONG — RCE if `query` contains "; rm -rf ~"
#[tauri::command]
fn search(query: String) -> Result<String, Error> {
    let out = std::process::Command::new("sh")
        .arg("-c")
        .arg(format!("grep {} ~/notes", query))
        .output()?;
    Ok(String::from_utf8_lossy(&out.stdout).into_owned())
}

// ✅ CORRECT — pass args directly, no shell
#[tauri::command]
fn search(query: String) -> Result<String, Error> {
    if query.len() > 200 { return Err(Error::TooLong); }
    let out = std::process::Command::new("grep")
        .arg("--")            // end of options
        .arg(&query)          // safe: passed as argv, no shell parsing
        .arg(notes_dir())
        .output()?;
    Ok(String::from_utf8_lossy(&out.stdout).into_owned())
}
Pattern 4: Missing Capability — Implicit Trust on a New Window
rust
// ❌ WRONG — created new window, didn't add capability — but ALSO didn't restrict commands
// New "settings" window can call EVERY command listed in invoke_handler if a wildcard capability exists
let _settings = WebviewWindowBuilder::new(&app, "settings", WebviewUrl::App("settings".into()))
    .build()?;

// ✅ CORRECT — explicit capability with minimum permissions for settings window
// src-tauri/capabilities/settings.json
{
  "identifier": "settings",
  "windows": ["settings"],
  "permissions": ["core:default", "settings:allow-read", "settings:allow-write"],
  "platforms": ["macOS"]
}
Pattern 5: CSP Allows Inline Script (XSS Amplifier)
json
// ❌ WRONG — any reflected XSS becomes RCE via invoke()
"csp": "default-src 'self'; script-src 'self' 'unsafe-inline'"

// ✅ CORRECT — Tauri injects nonces for bundled scripts; no inline needed
"csp": "default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; connect-src 'self' https://api.example.com"
Pattern 6: dangerousDisableAssetCspModification: true
json
// ❌ WRONG — disables Tauri's automatic nonce/hash injection
"app": { "security": { "dangerousDisableAssetCspModification": true } }

// ✅ CORRECT — leave default (false). Only enable if you have a strong CSP without it.
Pattern 7: Untyped Error Leaks Internals
rust
// ❌ WRONG — full path leaks to frontend (and into logs / crash reports)
#[tauri::command]
fn open_db() -> Result<(), String> {
    std::fs::File::open("/Users/alice/secrets.db").map_err(|e| e.to_string())?;
    Ok(())
}

// ✅ CORRECT — typed error rewrites messages
#[derive(thiserror::Error, Debug)]
enum DbError {
    #[error("database unavailable")]
    Unavailable,
}
impl serde::Serialize for DbError { /* serialize as string */ }
Pattern 8: Remote URL in Window Without Capability Audit
json
// ❌ WRONG — loading a third-party URL into a window with all permissions
{ "label": "embed", "url": "https://untrusted.example.com/widget" }
// + capability with broad permissions for "embed" window

// ✅ CORRECT — remote content gets a separate capability with NO commands granted
{
  "identifier": "embed-readonly",
  "windows": ["embed"],
  "permissions": ["core:event:default"],  // events only, no fs/shell/etc
  "remote": { "urls": ["https://untrusted.example.com/*"] }
}
Pattern 9: Open URL With User-Controlled String
rust
// tauri-plugin-shell's `open` is deprecated in Tauri v2; use tauri-plugin-opener.
use tauri_plugin_opener::OpenerExt;

// ❌ WRONG — "javascript:..." or arbitrary scheme
#[tauri::command]
fn open_link(url: String, app: AppHandle) {
    app.opener().open_url(&url, None::<&str>).ok();
}

// ✅ CORRECT — validate scheme + domain
#[tauri::command]
fn open_link(url: String, app: AppHandle) -> Result<(), Error> {
    let parsed = url::Url::parse(&url).map_err(|_| Error::InvalidUrl)?;
    if !matches!(parsed.scheme(), "https" | "http") { return Err(Error::InvalidScheme); }
    let host = parsed.host_str().ok_or(Error::InvalidUrl)?;
    if !["docs.example.com", "github.com"].contains(&host) { return Err(Error::DomainNotAllowed); }
    app.opener().open_url(parsed.as_str(), None::<&str>).map_err(|_| Error::OpenFailed)?;
    Ok(())
}
Pattern 10: Isolation Pattern Not Used For High-Risk IPC

When the app handles secrets (tokens, keys) and loads any remote/3rd-party content, enable Tauri's Isolation Pattern — it routes all IPC through a sandboxed inner iframe so a compromised main webview cannot forge invoke calls.


Severity Guide

SeverityExamplesAction
CRITICALPath traversal in command, shell injection, capability with $HOME/** write, CSP unsafe-eval, command exposed without capability check, secret leaked in errorBlock merge
HIGHOver-broad permission scope, missing input validation, unwrap() in command, unsafe-inline script, http (not https) connect-srcFix before merge
MEDIUMMissing platforms[] narrowing, missing description, weak error type, asset scope too broadFix in follow-up
LOWIdentifier naming, missing comments, unused permission entriesBacklog

Official Documentation References


  • Agent: tauri-security-reviewer
  • Commands: /tauri-review, /tauri-check, /tauri-audit

© mukiwu, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/tauri-security-review of mukiwu/tempo-term.

Open the folder on GitHubat commit 6750c17

Compare with similar skills

Tauri Security Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tauri Security Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tauri Security Review this skillmukiwu/tempo-term229—~2.8kAutomated safety check: NotesApache-2.0
Security Reviewdeadlock-mod-manager/deadlock-mod-manager478—~1.8kAutomated safety check: PassCC-BY-SA-4.0
Review Maple SecurityMaplePrivacyLabs/Maple102—~7.1kAutomated safety check: PassMIT
Security Auditwlsdks/ontology-atlas142—~182Automated safety check: PassMIT
Deepsec Documentation Guidevercel-labs/deepsec8.1k—~956Automated safety check: PassApache-2.0
Kubernetes Network Security Auditkubeshark/kubeshark12k—~7.3kAutomated safety check: NotesApache-2.0

Similar skills

  • Security Review

    deadlock-mod-manager/deadlock-mod-manager

    Security code review for Tauri/Rust/TypeScript desktop apps and Hono/oRPC APIs.

    478 GitHub stars~1.8k tokensUpdated today
    SecurityAuto-check passed
  • Review Maple Security

    MaplePrivacyLabs/Maple

    Review Maple security across authentication, account isolation, local persistence, Tauri IPC and capabilities, OAuth and deep links, the Local OpenAI Proxy, Agent Mode tools and permissions, MCP…

    102 GitHub stars~7.1k tokensUpdated today
    SecurityAuto-check passed
  • Security Audit

    wlsdks/ontology-atlas

    Periodic security sweep of Atlas in four areas (MCP and CLI, the Tauri desktop shell, the web renderer and connectors, the supply chain and CI) that follows untrusted input to what it can reach…

    142 GitHub stars~182 tokensUpdated today
    SecurityAuto-check passed
  • Deepsec Documentation Guide

    vercel-labs/deepsec

    Official

    Points the agent at deepsec's own docs to answer questions about initializing, configuring, resuming, scanning with and extending the vulnerability scanner.

    8.1k GitHub stars~956 tokensUpdated 11 days ago
    SecurityAuto-check passed
  • Hunts for compromised workloads and malicious traffic in a Kubernetes cluster by sweeping network data through Kubeshark MCP, mapped to MITRE ATT&CK.

    12k GitHub stars~7.3k tokensUpdated yesterday
    SecurityAuto-check: notes
  • Update native dependencies (libpng, libexpat, zlib, libwebp, harfbuzz, freetype, libjpeg-turbo, etc.) in SkiaSharp's Skia fork.

    5.6k GitHub stars~4.1k tokensUpdated today
    SecurityAuto-check passed

More from mukiwu/tempo-term

  • Tauri

    mukiwu/tempo-term

    A skill your agent uses when working with Tauri 2 projects (tauri.conf.json, src-tauri/, capabilities, permissions,

    229 GitHub stars~2.5k tokensUpdated 10 days ago
    Auto-check passed
  • Windows Tauri

    mukiwu/tempo-term

    A skill your agent uses when writing or reviewing code in this Tauri app that can behave differently on Windows — spawning a subprocess (git/gh/any Command), path handling, cfg-gated platform APIs…

    229 GitHub stars~4.3k tokensUpdated 10 days ago
    Auto-check passed
  • Tauri Performance Review

    mukiwu/tempo-term

    Expert workflow for reviewing Tauri 2 desktop app performance.

    229 GitHub stars~2.4k tokensUpdated 10 days ago
    Auto-check passed

Works with

Categories

Questions about Tauri Security Review

What does Tauri Security Review do?

Expert workflow for reviewing Tauri 2 desktop app security. An agent skill from mukiwu/tempo-term. Tauri Security Review is an agent skill from mukiwu/tempo-term. Expert workflow for reviewing Tauri 2 desktop app security.

When should I use Tauri Security Review?

Tauri Security Review fits situations like: tasks that involve Security review.

How do I install Tauri Security Review in Claude Code?

Run `npx skills add mukiwu/tempo-term --skill tauri-security-review -a claude-code`. Or copy the skill folder (.claude/skills/tauri-security-review in mukiwu/tempo-term) into .claude/skills/tauri-security-review in your project. Claude Code loads it when a task matches its description.

How do I install Tauri Security Review in Codex?

Run `npx skills add mukiwu/tempo-term --skill tauri-security-review -a codex`. Or copy the skill folder (.claude/skills/tauri-security-review in mukiwu/tempo-term) into .agents/skills/tauri-security-review in your project. Codex loads it when a task matches its description.

Can I use Tauri Security Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukiwu/tempo-term --skill tauri-security-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tauri-security-review, .gemini/skills/tauri-security-review, .github/skills/tauri-security-review and .opencode/skills/tauri-security-review in your project.

What does Tauri Security Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Tauri Security Review is instructions for the agent only.

Does Tauri Security Review access the network?

SKILL.md names 1 domain. As links in the text: v2.tauri.app. This is read from the text; nothing was executed.

Is Tauri Security Review safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Tauri Security Review use?

Tauri Security Review is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tauri Security Review use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Tauri Security Review?

Skills that share tags, products or a category with Tauri Security Review: Security Review (deadlock-mod-manager/deadlock-mod-manager, 478 stars), Review Maple Security (MaplePrivacyLabs/Maple, 102 stars), Security Audit (wlsdks/ontology-atlas, 142 stars) and Deepsec Documentation Guide (vercel-labs/deepsec, 8.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tauri Security Review?

mukiwu (a GitHub user) maintains it in mukiwu/tempo-term, which has 229 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 30, 2026.

Source: mukiwu/tempo-term on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.