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/mutationsgit 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/mutations)<a href="https://agentmods.dev/commands/cesarandreslopez/tauri-agent-tools/mutations"><img src="https://agentmods.dev/badge/commands/cesarandreslopez/tauri-agent-tools/mutations.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.00509 |
| Opus 5 | $0.00000 | $0.00254 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
mutations 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mutations
Watch DOM mutations on a CSS selector in real-time (read-only).
!!! note "Bridge Required" This command requires an active bridge connection.
Usage
tauri-agent-tools mutations <selector> [options]
Options
| Option | Description | Default |
|---|---|---|
<selector> |
CSS selector of the element to observe | (required) |
--attributes |
Also watch attribute changes | — |
--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
Watch for child additions/removals
tauri-agent-tools mutations "#todo-list" --duration 10000
[14:30:00.500] childList #todo-list +.todo-item
[14:30:02.100] childList #todo-list -.todo-item
Watch attribute changes too
tauri-agent-tools mutations ".sidebar" --attributes --duration 5000
[14:30:01.200] attr .sidebar class: sidebar → sidebar expanded
JSON output for automation
tauri-agent-tools mutations "#app" --json --duration 10000
Quick 5-second observation
tauri-agent-tools mutations "body" --duration 5000 --interval 200
How It Works
- Patches a
MutationObserverinto the webview targeting the specified selector - Polls the accumulated mutation log at the configured interval
- Formats and outputs each mutation entry
- Disconnects the observer and cleans up global state on exit (Ctrl+C, SIGTERM, or
--duration)
Important Notes
- Always use
--durationin automation to avoid indefinite execution. - The observer watches
childListandsubtreeby default. Add--attributesto also track attribute changes. - If a previous session didn't clean up (e.g., hard kill), the command will warn and drain the existing log.
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 · 73 lines · 0 tokens per session scan A a8b71dac9c8f
mutations 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 509 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
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
recette
Tests d'acceptance automatises avec Claude in Chrome.
run-action
Execute a learned Maestro flow ("action") by name with optional -e KEY=VALUE parameters. Looks the flow up via packages/rn-dev-agent-core/dist/learned-actions.js (same inventory as /rn-dev-agent:list-learned-actions), then replays it via cdprunaction — auto-repair-aware orchestration with structured RunRecords (GH.
nodebench-qa
Full QA loop: crawl → findings → fix suggestions → re-crawl → savings report.
run-test
Execute AI agent test script in real browser.
can-i-use
Check browser support for web platform features against the project's browser targets.