tauri-agent-tools: Instructions file for Codex

AGENTS.md

tauri-agent-tools AGENTS.md is an instructions file for Codex, OpenCode from cesarandreslopez/tauri-agent-tools. It costs 903 tokens per session, scanned A, original, MIT.

Repository instructions for tauri-agent-tools, a command-line tool for inspecting and debug-interacting with Tauri desktop apps. They also describe three related agent skills and which commands work without a development bridge.

In plain words
What is it for?
Use them to install the tool, inspect windows and screenshots, examine logs and app files, compare output, or set up and use its Tauri development bridge.
Why use it?
They help an agent choose the right diagnostic command and understand which operations are read-only or require the app's debug bridge.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is cesarandreslopez/tauri-agent-tools's own configuration. It tells Codex and OpenCode how to work on tauri-agent-tools itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything tauri-agent-tools configures →

Reuse

Borrowing it

Nothing to install: this file belongs to cesarandreslopez/tauri-agent-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/cesarandreslopez/tauri-agent-tools/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/cesarandreslopez/tauri-agent-tools

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for tauri-agent-tools AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/cesarandreslopez/tauri-agent-tools/agents-md/github.svg)](https://agentmods.dev/instructions/cesarandreslopez/tauri-agent-tools/agents-md)
Your own site
<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/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.

agentmods 80×15 button for tauri-agent-tools AGENTS.md

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 903 This file is loaded in full into every session.
When invoked 903 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00903 $0.00903
Opus 5.5 $0.00361 $0.00361
Sonnet 5.5 $0.00181 $0.00181
Haiku 4.5 $0.00090 $0.00090

Measured 1mo ago against content hash 97c620dfa368, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

AGENTS.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 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

DOM, screenshot, and storage inspection read app state. eval can modify app state. Monitors install temporary instrumentation. 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 (use bridge v0.7+ for full output; 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)

Read the full file on GitHub · 52 lines

Changes

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.

  1. 1mo ago Changed · +4 lines · +166 tokens per session 97c620dfa368
  2. 1mo ago First seen · 48 lines · 737 tokens per session scan A f0c149e41884

Subscribe to this mod's changes

tauri-agent-tools AGENTS.md is an instructions file published in the GitHub repository cesarandreslopez/tauri-agent-tools (24 stars, last pushed 1mo ago), licensed MIT. It adds 903 tokens to every session, about $0.0036 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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,649 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,549 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens