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 skills/xiaolai/vmark/tauri-mcp-testingnpx skills add xiaolai/vmark --skill tauri-mcp-testinggit clone --depth 1 https://github.com/xiaolai/vmarkWrote 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/skills/xiaolai/vmark/tauri-mcp-testing)<a href="https://agentmods.dev/skills/xiaolai/vmark/tauri-mcp-testing"><img src="https://agentmods.dev/badge/skills/xiaolai/vmark/tauri-mcp-testing.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.00062 | $0.02703 |
| Opus 5 | $0.00031 | $0.01352 |
| Sonnet 5 | $0.00012 | $0.00541 |
| Haiku 4.5 | $0.00006 | $0.00270 |
Grade A, and why
tauri-mcp-testing 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 — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tauri MCP E2E Testing
CRITICAL: For E2E testing of Tauri applications, ALWAYS use tauri_* MCP tools. NEVER use Chrome DevTools MCP - that's for browser pages only.
Quick Reference
| Task | MCP Tool |
|---|---|
| Connect to app | tauri_driver_session |
| Take screenshot | tauri_webview_screenshot |
| Find elements | tauri_webview_find_element |
| Click/scroll/swipe | tauri_webview_interact |
| Type text | tauri_webview_keyboard |
| Wait for element | tauri_webview_wait_for |
| Execute JS | tauri_webview_execute_js |
| Get CSS styles | tauri_webview_get_styles |
| Test IPC commands | tauri_ipc_execute_command |
| Monitor IPC calls | tauri_ipc_monitor |
| Read console logs | tauri_read_logs |
| Manage windows | tauri_manage_window |
Prerequisites
- MCP Bridge Plugin installed in the Tauri app
- App running in development mode (
pnpm tauri:dev) - Port 9323 accessible for VMark automation. VMark pins the debug-only
Tauri MCP bridge to
127.0.0.1:9323; port 9223 is VMark's own auth-protected MCP server and is not valid for E2E automation.
If connection fails, run tauri_get_setup_instructions to get plugin installation guide.
Core Workflow
1. START SESSION → Connect to running Tauri app
2. VERIFY STATE → Screenshot + find elements
3. INTERACT → Click, type, scroll
4. WAIT → Wait for expected results
5. VERIFY → Check IPC, logs, DOM state
6. CLEANUP → Stop session when done
Session Management
Start Session
// Connect to VMark's automation bridge
tauri_driver_session({ action: 'start', port: 9323 })
// Connect to specific port
tauri_driver_session({ action: 'start', port: 9324 })
// Connect to remote host (mobile testing)
tauri_driver_session({ action: 'start', host: '<device-ip>', port: 9323 })
Check Status
tauri_driver_session({ action: 'status' })
// Returns: connected apps, default app, identifiers
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 387 lines · 62 tokens per session scan A a7848ee85875
tauri-mcp-testing is a skill published in the GitHub repository xiaolai/vmark (548 stars, last pushed 2d ago), licensed ISC. It adds 62 tokens to every session and 2,703 once invoked, about $0.0003 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 skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…
agent-device-evidence
Records iOS/Android native MP4 evidence for test/repro flows extracted from an Expensify GitHub PR or issue. Use when the user asks to "record the flow for PR.