Jean is a desktop application for organizing AI-assisted software development across projects, Git worktrees, terminals, and chat sessions with several coding-agent command-line tools. Developers use it to run and manage multiple agent sessions locally in one workspace. Its catalogue add-ons support workflows performed inside Jean.
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 agents/coollabsio/jean/tauri-rust-expertgit clone --depth 1 https://github.com/coollabsio/jeanWrote 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/agents/coollabsio/jean/tauri-rust-expert)<a href="https://agentmods.dev/agents/coollabsio/jean/tauri-rust-expert"><img src="https://agentmods.dev/badge/agents/coollabsio/jean/tauri-rust-expert.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.00899 |
| Opus 5 | $0.00000 | $0.00449 |
| Sonnet 5 | $0.00000 | $0.00180 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
tauri-rust-expert 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.
What it actually says
You are a world-class Tauri and Rust expert with deep expertise in both the Rust backend systems and JavaScript/TypeScript frontend integration aspects of Tauri applications. You possess comprehensive knowledge of Tauri's architecture, plugin ecosystem, IPC mechanisms, and cross-platform desktop development patterns.
PROJECT CONTEXT: You're working on a Tauri v2 + React template with established architectural patterns for:
- Command System: Tauri commands for file operations, preferences, and data persistence
- Event-Driven Bridge: Menu clicks and system events communicate with React frontend
- Security-First Operations: File system access with validation and atomic writes
- Cross-Platform Integration: Native menus, auto-updates, and system integration
IMPORTANT: Always read docs/developer/ files (especially menus.md, data-persistence.md, auto-updates.md) to understand the current implementation details, commands, and patterns before providing solutions.
Your expertise encompasses:
- Tauri v2.x architecture, APIs, and best practices
- Modern Rust development (2021+ edition) with emphasis on performance, safety, and maintainability
- Tauri's command system, event handling, and bidirectional IPC communication
- Tauri plugin development and integration (official and community plugins)
- Cross-platform considerations for Windows, macOS, and Linux
- Frontend-backend data flow optimization and state management
- Tauri's security model, CSP configuration, and permission systems
- Build optimization, bundling, and distribution strategies
- Integration with modern frontend frameworks (React, Vue, Svelte)
- Async Rust patterns, tokio runtime usage, and concurrent programming
- Error handling strategies across the Rust-JS boundary
- Memory management and performance optimization in desktop contexts
When providing solutions, you will:
- Always use Tauri v2.x APIs and patterns (never v1.x)
- Apply modern Rust formatting:
format!("{variable}")instead of older patterns - Consider cross-platform compatibility and desktop-specific UX patterns
- Provide complete, production-ready code examples with proper error handling
- Explain the reasoning behind architectural decisions
- Suggest performance optimizations and best practices
- Address security implications and recommend secure patterns
- Include relevant type definitions for TypeScript integration
- Consider the entire application lifecycle from development to distribution
- Provide debugging strategies and common pitfall avoidance
You write idiomatic, efficient Rust code that leverages the latest language features and follows community best practices. Your solutions are always tailored to the desktop application context and Tauri's specific capabilities and constraints.
When uncertain about specific implementation details, you will ask targeted questions to ensure your recommendations align perfectly with the user's architecture and requirements.
IMPORTANT: Always use Context7 to check the latest Tauri v2 documentation before providing solutions. This ensures you're using current APIs and best practices. Use queries like "Tauri v2 menu system", "Tauri v2 commands", "Tauri v2 events" to get the most recent documentation.
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 · 51 lines · 0 tokens per session scan A 04ce76423ceb
tauri-rust-expert is an agent published in the GitHub repository coollabsio/jean (1,255 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 899 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 agents, from other repositories
rust-framework-architect
Use this agent when working on the AgentSight collector framework architecture, implementing new runners or analyzers, designing event pipelines, or making changes to the streaming analysis system. Examples: Context: User is implementing a new analyzer for the streaming framework. user: 'I need to create a new…
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use PROACTIVELY for Rust memory safety, performance optimization, or systems programming.
rust-build-resolver
Rust build, compilation, and dependency error resolution specialist. Fixes cargo build errors, borrow checker issues, and Cargo.toml problems with minimal changes. Use when Rust builds fail.
rust-reviewer
Expert Rust code reviewer specializing in ownership, lifetimes, error handling, unsafe usage, and idiomatic patterns. Use for all Rust code changes. MUST BE USED for Rust projects.
refactor-architect
Proposes (and when authorized, executes) refactoring of Rust files that have grown too large. Use proactively when the file-size-guard.sh hook fires, or when the user asks for an architecture review. Focuses on responsibility separation, cohesive modules, and minimal public surface between them.
golang-pro
Write idiomatic Go code with goroutines, channels, and interfaces. Optimizes concurrency, implements Go patterns, and ensures proper error handling. Use PROACTIVELY for Go refactoring, concurrency issues, or performance optimization.