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/rust-logsgit 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/rust-logs)<a href="https://agentmods.dev/commands/cesarandreslopez/tauri-agent-tools/rust-logs"><img src="https://agentmods.dev/badge/commands/cesarandreslopez/tauri-agent-tools/rust-logs.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.00000 | $0.00959 |
| Opus 5 | $0.00000 | $0.00479 |
| Sonnet 5 | $0.00000 | $0.00192 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
rust-logs 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rust-logs
Monitor Rust backend logs and sidecar output in real-time.
!!! note "Bridge Required"
This command requires an active bridge connection with the updated dev_bridge.rs that supports the /logs endpoint.
Usage
tauri-agent-tools rust-logs [options]
Options
| Option | Description | Default |
|---|---|---|
--level <level> |
Minimum log level: trace, debug, info, warn, error |
— |
--target <regex> |
Filter by Rust module path (regex) | — |
--source <source> |
Filter by source: rust, sidecar, all, or sidecar:<name> |
all |
--filter <regex> |
Filter messages by regex pattern | — |
--interval <ms> |
Poll interval in milliseconds | 500 |
--duration <ms> |
Auto-stop after N milliseconds | — |
--json |
Output one JSON object per line | — |
--port <number> |
Bridge port (auto-discover if omitted) | — |
--token <string> |
Bridge token (auto-discover if omitted) | — |
Examples
Monitor all Rust logs
tauri-agent-tools rust-logs
Monitoring Rust logs... (Ctrl+C to stop)
[12:34:56.789] [INFO] myapp::db: Connected to database
[12:34:57.123] [WARN] myapp::api: Rate limit approaching
[12:34:57.456] [ERROR] myapp::auth: Token expired for user 42
Only show warnings and errors
tauri-agent-tools rust-logs --level warn
Level filtering is severity-based (like RUST_LOG): --level warn shows warn and error, filtering out trace, debug, and info.
Filter by module path
tauri-agent-tools rust-logs --target "myapp::db"
The --target option accepts a regex, so myapp::db matches myapp::db, myapp::db::pool, etc.
Monitor sidecar output only
tauri-agent-tools rust-logs --source sidecar
Or filter to a specific sidecar:
tauri-agent-tools rust-logs --source sidecar:ffmpeg
Auto-stop after 30 seconds
tauri-agent-tools rust-logs --duration 30000 --level info
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 · 115 lines · 0 tokens per session scan A 8bba20e2d0cf
rust-logs 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 959 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
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.
dataviz
Define chart types, color encoding, and data display conventions.
a11y
Audit and fix WCAG AA compliance — semantic HTML, ARIA, keyboard, contrast, reduced-motion.
api
Design REST endpoints with consistent error envelopes, versioning, pagination, and idempotency.
brand
Define brand foundations, voice, tone, and visual identity rules.
build
Implement the next ready task from .forge/tasks.yaml using TDD discipline.