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 commands/cesarandreslopez/tauri-agent-tools/infogit 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/commands/cesarandreslopez/tauri-agent-tools/info)<a href="https://agentmods.dev/commands/cesarandreslopez/tauri-agent-tools/info"><img src="https://agentmods.dev/badge/commands/cesarandreslopez/tauri-agent-tools/info.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 | $0.00000 | $0.00479 |
| Opus 5 | $0.00000 | $0.00239 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
info 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 5d 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.
What it actually says
info
Show window geometry and display server info.
!!! success "No Bridge Required" This command works with any window — no Tauri bridge needed.
Usage
tauri-agent-tools info (--title <regex> | --window-id <id>) [options]
Options
| Option | Description | Default |
|---|---|---|
-t, --title <regex> |
Window title to match — regex; quote titles with spaces | — |
-w, --window-id <id> |
Platform window id (from list-windows) — overrides --title |
— |
--json |
Output as JSON | — |
One of --title or --window-id is required.
Examples
Text output
tauri-agent-tools info --title "My App"
Window ID: 12345678
Name: My Tauri App
Position: 100, 50
Size: 1920x1080
Display Server: x11
JSON output
tauri-agent-tools info --title "My App" --json
{
"windowId": "12345678",
"pid": 1234,
"name": "My Tauri App",
"x": 100,
"y": 50,
"width": 1920,
"height": 1080,
"displayServer": "x11"
}
By window id
tauri-agent-tools info --window-id 12345678
Notes
- The
--titleflag accepts a regex pattern for matching --window-idskips the title search entirely — take the id fromlist-windows --json(windowIdfield); its format is platform-specific (X11/macOS/Sway numeric, Hyprland hex0x…)--window-id(platform/OS window) is unrelated to--window-label(Tauri webview label, a bridge concept)- Window geometry includes decoration (title bar, borders)
- Display server is one of:
x11,wayland,darwin
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.
- 5d ago First seen · 72 lines · 0 tokens per session scan A b115e016f52b
info is a command published in the GitHub repository cesarandreslopez/tauri-agent-tools (22 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 479 tokens. 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 commands, from other repositories
fact-check
Fact-check claims or verify information.
competitive-analysis
Perform competitive analysis on companies or products.
market-trends
Research current market trends in a specific industry or domain.
research
Start a focused research session on any topic.
summarize
Summarize all current research findings.
commands
This file defines the slash commands that drive the Jump Start workflow. Each command activates a specific agent or system function. These definitions are consumed by the AI assistant integration layer to route commands to the correct agent persona and instructions.