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 instructions/hushlor/mcp-server-tauri/agents-mdgit clone --depth 1 https://github.com/Hushlor/mcp-server-tauriWrote 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/instructions/hushlor/mcp-server-tauri/agents-md)<a href="https://agentmods.dev/instructions/hushlor/mcp-server-tauri/agents-md"><img src="https://agentmods.dev/badge/instructions/hushlor/mcp-server-tauri/agents-md.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.02942 | $0.02942 |
| Opus 5 | $0.01471 | $0.01471 |
| Sonnet 5 | $0.00588 | $0.00588 |
| Haiku 4.5 | $0.00294 | $0.00294 |
Grade A, and why
mcp-server-tauri 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 4d 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.
This is a copy
86% identical to mcp-server-tauri AGENTS.md — 52 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project Overview
MCP server for Tauri v2 application development. Provides tools for CLI execution, configuration management, mobile device/emulator management, native UI automation, and debugging.
Monorepo packages:
packages/mcp-server/- Main MCP server implementationpackages/tauri-plugin-mcp-bridge/- Tauri plugin for automation bridge (Rust)packages/test-app/- Test application for E2E testingpackages/cli- A CLI wrapper for the MCP server funcionality
Setup Commands
npm install # Install all dependencies
npm run build # Build all packages
npm test # Run tests (requires build first)
npm run standards # Run commitlint + eslint
Code Style
- TypeScript: Strict mode, ESM with
.jsextensions in imports, ES2022 target - Naming: camelCase for functions/variables, PascalCase for classes, kebab-case for files
- Acronyms: All lowercase or all caps, never mixed (e.g.,
urlorURL, neverUrl) - Avoid:
anytype, magic numbers, deeply nested blocks - Prefer: Early returns, higher-order functions, immutability (
readonly,as const) - Functions: Arrow for simple (<3 instructions), named otherwise; use RO-RO pattern
- JSDoc: Document public classes and methods
Adding New MCP Tools
All tools are defined in packages/mcp-server/src/tools-registry.ts:
- Add Zod schema + handler in the appropriate module (
manager/,driver/,monitor/) - Import and add entry to
TOOLSarray intools-registry.ts - Add E2E test in
packages/mcp-server/tests/e2e/
Tool categories: PROJECT_MANAGEMENT, MOBILE_DEVELOPMENT, UI_AUTOMATION, IPC_PLUGIN
Testing Instructions
- Always build before testing:
npm run build - E2E tests launch
test-appand connect via WebSocket - Tests located in
packages/mcp-server/tests/e2e/ - Prefer E2E tests over unit tests
- CI timeout is 8 minutes; local is 1 minute
Manual MCP Testing (local dev MCP server)
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.
- 4d ago First seen · 217 lines · 2,942 tokens per session scan A cb91d50b8e9e
mcp-server-tauri AGENTS.md is an instructions file published in the GitHub repository Hushlor/mcp-server-tauri (0 stars, last pushed 9d ago), licensed MIT. It adds 2,942 tokens to every session, about $0.0147 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to mcp-server-tauri AGENTS.md, differing in 52 lines, and is treated as a copy.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).