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 agentmods add instructions/cesarandreslopez/tauri-agent-tools/agents-mdgit 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/instructions/cesarandreslopez/tauri-agent-tools/agents-md)<a href="https://agentmods.dev/instructions/cesarandreslopez/tauri-agent-tools/agents-md"><img src="https://agentmods.dev/badge/instructions/cesarandreslopez/tauri-agent-tools/agents-md.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.00737 | $0.00737 |
| Opus 5 | $0.00368 | $0.00368 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
tauri-agent-tools AGENTS.md 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 6d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tauri-agent-tools
CLI tool for agent-driven inspection and interaction with Tauri desktop applications. Not an MCP server — invoke commands directly via shell.
Agent Skills
This package includes three Agent Skills:
| Skill | Path | Purpose |
|---|---|---|
tauri-agent-tools |
.agents/skills/tauri-agent-tools/SKILL.md |
Using all 38 CLI commands to inspect and interact with Tauri apps |
tauri-bridge-setup |
.agents/skills/tauri-bridge-setup/SKILL.md |
Adding the Rust dev bridge to a Tauri project |
tauri-debug-quickstart |
.agents/skills/tauri-debug-quickstart/SKILL.md |
First-30-seconds triage — pick the right command for the symptom |
Quick Reference
Install: npm install -g tauri-agent-tools
Inspection commands are read-only. Interaction commands (click, type, scroll, etc.) are debug-only — they only work with the dev bridge.
Standalone commands (no bridge needed):
list-windows, info, screenshot --title, wait --title, diff
Bridge-free diagnostics (work on release builds, dead apps, and sidecars — no bridge required):
app-paths, config inspect, os-logs, sidecar tap, sidecar replay, forensics, logs (also reads the live bridge ring buffer when present), process-tree --deep (walks the full OS descendant tree)
Bridge-required commands (Tauri app must have dev bridge running):
dom, eval, screenshot --selector, wait --selector/--eval, ipc-monitor, console-monitor, rust-logs, storage, page-state, mutations, snapshot, click, type, scroll, focus, navigate, select, invoke, capture, check, store-inspect
Bridge-extending diagnostics (require bridge v0.7+; degrade gracefully against older/vendored bridges, or pass --strict to fail):
process-tree, capabilities audit, webview attach, health
Super-commands (best-effort, compose the above):
diagnose (one-shot triage report), bundle (shareable, redacted incident archive → directory + .tar.gz)
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.
- 6d ago First seen · 48 lines · 737 tokens per session scan A f0c149e41884
tauri-agent-tools AGENTS.md is an instructions file published in the GitHub repository cesarandreslopez/tauri-agent-tools (22 stars, last pushed 12d ago), licensed MIT. It adds 737 tokens to every session, about $0.0037 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-08-30.
Other instructions, from other repositories
dev3000 AGENTS.md
Instructions for vercel-labs/dev3000, covering agents.md, runtime, local ui, production workflows, browser tools and development rules.
agent-inspect AGENTS.md
AGENTS.md instructions for rajudandigam/agent-inspect, covering agentinspect ai maintainer instructions, product boundary, source of truth, public-copy rule and start every task.
aidevops codacy.instructions.md
Configuration for AI behavior when interacting with Codacy's MCP Server.
jenkins-cli CLAUDE.md
Claude Code instructions for avivsinai/jenkins-cli, covering claude.md, build & test commands, run a single test, skip e2e tests during unit testing and e2e with colima on macos (if docker is unreachable).
autovault CLAUDE.md
Claude Code instructions for autoworks-ai/autovault, covering claude.md, project, common commands, architecture and request flow.
aiworkspace AGENTS.md
Instructions for a-tokyo/aiworkspace, covering ai workspace, structure, key commands, conventions and code quality.