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 cesarandreslopez/tauri-agent-tools --skill tauri-debug-quickstartgit clone --depth 1 https://github.com/cesarandreslopez/tauri-agent-toolsWrote 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/cesarandreslopez/tauri-agent-tools/tauri-debug-quickstart)<a href="https://agentmods.dev/skills/cesarandreslopez/tauri-agent-tools/tauri-debug-quickstart"><img src="https://agentmods.dev/badge/skills/cesarandreslopez/tauri-agent-tools/tauri-debug-quickstart/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/cesarandreslopez/tauri-agent-tools/tauri-debug-quickstart"><img src="https://agentmods.dev/badge/skills/cesarandreslopez/tauri-agent-tools/tauri-debug-quickstart.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.01666 |
| Opus 5.5 | $0.00016 | $0.00666 |
| Sonnet 5.5 | $0.00008 | $0.00333 |
| Haiku 4.5 | $0.00004 | $0.00167 |
Grade A, and why
tauri-debug-quickstart 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 1mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tauri Debug Quickstart
When something is wrong with a Tauri app, the first 30 seconds matter — they decide whether you spend the next hour reading the right logs or the wrong ones. This skill points you at the right tauri-agent-tools command for the symptom you're seeing.
The single-command answer
If you don't know where to start, run this first:
tauri-agent-tools diagnose --config ./src-tauri -o ./diagnose-out
diagnose is a best-effort super-command that:
- Resolves the app's config + OS data/log paths
- Runs a forensics bundle (works even on dead apps — tails app logs for panics, pulls macOS DiagnosticReports, lists app-data files)
- If a live dev bridge is reachable, layers
/process,/capabilities,/devtools,/healthdata on top - Writes a master
summary.mdwith detected anomalies and suggested next steps
Then open ./diagnose-out/summary.md and follow the "Next steps" section.
Symptom → command (when you need precision)
Pick the row that matches what's broken. Each command works without the bridge unless noted.
| Symptom | First command | Why |
|---|---|---|
| Don't know what's wrong | tauri-agent-tools diagnose -o ./diag |
Everything-bundle; graceful on dead apps |
| App crashed at startup | tauri-agent-tools forensics --config ./src-tauri -o ./forensics |
Reads app log + DiagnosticReports without needing a live process |
| App is running but bridge isn't responding | tauri-agent-tools probe |
Detects whether the bridge process is up and shows token-file state |
| App is running, bridge is up, but webview looks wrong | tauri-agent-tools health --json |
Returns webview_ready + sidecar liveness (richer on bridge v0.7+; degrades to a liveness ping otherwise) |
| Evidence is scattered across webview/Rust/sidecar logs | tauri-agent-tools logs --config ./src-tauri --pretty |
Merges on-disk log files + the bridge ring buffer into one timestamp-ordered timeline |
| Need to watch logs live while reproducing | tauri-agent-tools logs --follow --pretty |
Needs bridge; multi-consumer-safe on bridge v0.8+, drain-polling fallback otherwise |
| What did the sidecar actually spawn (MCP servers, workers)? | tauri-agent-tools process-tree --deep --json |
Walks the real OS descendant tree, including unregistered grandchildren — no bridge needed |
| Need one shareable archive of everything for a bug report | tauri-agent-tools bundle --config ./src-tauri -o ./triage |
Logs + deep process tree + app-paths + forensics → redacted dir + .tar.gz |
| A sidecar process is the suspect | tauri-agent-tools sidecar tap --schema ./schema.json -- <cmd> |
Wrap-and-run the sidecar standalone; frame NDJSON; validate envelopes |
| Need to know exactly which files the app touches | tauri-agent-tools app-paths --config ./src-tauri --exists |
Resolves Tauri 2's per-platform app_data_dir/app_log_dir/etc. + checks existence |
| Need to audit Tauri capabilities for over-broad permissions | tauri-agent-tools config inspect --config ./src-tauri (static) or tauri-agent-tools capabilities audit (live, needs bridge v0.7+) |
Flags *, fs:allow-all, shell:allow-spawn, etc. |
| OS-level error visible in Console.app or journalctl | tauri-agent-tools os-logs --identifier com.example.app --level error --duration 30000 |
Filters platform log stream to the Tauri bundle id |
| Inspector / webview attach | tauri-agent-tools webview attach (needs bridge v0.7+) |
Returns inspector URL or platform-specific hint |
| What sidecars did this app spawn? | tauri-agent-tools process-tree --json (or --deep) |
Bridge /process lists registered sidecars (v0.7+); --deep walks the OS tree with no bridge |
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.
- 1mo ago Changed · +2 lines 9f11b2ca2330
- 1mo ago First seen · 85 lines · 41 tokens per session scan A ebe157774e98
tauri-debug-quickstart is a skill published in the GitHub repository cesarandreslopez/tauri-agent-tools (24 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,666 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
agent-qa-result-triage
Triage failed Agent QA runs with MCP evidence, artifacts, logs, fixed failure categories, confidence, and actionable next steps.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
vs-search-tuning-partial-case
Use when the user provides 1-50 concrete bad-case search queries for one Viking Search app and wants local deterministic fixes. This skill only verifies request-level fine-operation interventions against a read-only baseline scene and delivers a console-ready configuration sheet, validated payloads, and a replay…
gcp-cloud-logging
Google Cloud Logging — log search, VPC flow logs, firewall logs, audit logs, log buckets and views. Use when searching GCP logs, investigating denied VPC flow traffic, checking who deleted a VM, analyzing firewall rule hits, or troubleshooting a GCP application error.
bug-reporting-excellence
Write high-quality bug reports that get fixed quickly. Use when reporting bugs, training teams on bug reporting, or establishing bug report standards.