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 skills add OpenAEC-Foundation/OpenAEC-Workspace-Composer --skill tauri-core-architecturegit clone --depth 1 https://github.com/OpenAEC-Foundation/OpenAEC-Workspace-ComposerWrote 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/openaec-foundation/openaec-workspace-composer/tauri-core-architecture)<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/tauri-core-architecture"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/tauri-core-architecture/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/tauri-core-architecture"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/tauri-core-architecture.svg" alt="Reviewed on agentmods" width="80" 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.00094 | $0.03063 |
| Opus 5 | $0.00047 | $0.01532 |
| Sonnet 5 | $0.00019 | $0.00613 |
| Haiku 4.5 | $0.00009 | $0.00306 |
Grade A, and why
tauri-core-architecture 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 11d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tauri-core-architecture
Quick Reference
Architecture Layers (Tauri 2.x)
| Layer | Technology | Location | Role |
|---|---|---|---|
| Rust Backend | Rust + Tokio | src-tauri/src/ |
Application logic, system access, state management |
| Webview Layer | Platform-native webview | Embedded | Renders HTML/CSS/JS frontend |
| IPC Bridge | JSON-serialized messages | Internal | Connects frontend to backend via invoke() and events |
| Plugin System | Rust crate + npm package | Cargo.toml + package.json |
Extends capabilities (fs, dialogs, HTTP, etc.) |
| Permission System | Capabilities + permissions | src-tauri/capabilities/ |
Fine-grained access control (replaces v1 allowlist) |
Platform Webview Engines
| Platform | Webview Engine |
|---|---|
| Windows | WebView2 (Chromium-based) |
| macOS | WKWebView |
| Linux | WebKitGTK |
| iOS | WKWebView |
| Android | Android WebView |
Key Dependencies
| Package | Type | Purpose |
|---|---|---|
@tauri-apps/cli |
devDependency (npm) | CLI tooling for dev/build |
@tauri-apps/api |
dependency (npm) | Frontend API for invoke, events, paths |
tauri |
dependency (Cargo) | Core Rust framework |
tauri-build |
build-dependency (Cargo) | Build script helpers |
serde + serde_json |
dependency (Cargo) | Serialization for IPC |
Critical Warnings
NEVER block the main thread with synchronous I/O in commands -- ALWAYS use async for file, network, or long-running operations. Blocking freezes the entire UI.
NEVER call .invoke_handler() more than once on Builder -- only the LAST call takes effect. Put ALL commands in a single generate_handler![] macro.
NEVER mark command functions as pub when defined directly in lib.rs -- the glue code generation prevents it. Move commands to a separate module if they need to be public.
NEVER wrap managed state in Arc -- Tauri wraps state in Arc internally. Using app.manage(Arc::new(data)) adds a redundant layer.
What ships with it
3 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.
- 11d ago First seen · 303 lines · 94 tokens per session scan A ee02e27895fd
tauri-core-architecture is a skill published in the GitHub repository OpenAEC-Foundation/OpenAEC-Workspace-Composer (5 stars, last pushed 5mo ago), licensed MIT. It adds 94 tokens to every session and 3,063 once invoked, about $0.0005 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-31.
Other skills, from other repositories
add-tauri-command
Use when adding a new Tauri command to Cowork-Z — a new backend capability the React frontend must call, a new #[tauri::command] fn, or a new invoke() wrapper in tauri-api.ts. Also use when a newly written command returns "Command not found" at runtime.
fullstack-dev
Implement features that span backend and frontend together — API endpoints with their UI, auth flows, CRUD modules, validation. Use when the subtask requires both sides of the system to ship a working feature.
ipc-communication
Use when adding or debugging Electron IPC between preload, renderer, and main; implements strongly typed send/invoke/receive channels, payload contracts, window.electron API wiring, and safe handler registration.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
service-digital-engagement-channel-configure
Configures and deploys enhanced chat Messaging Channels for Messaging for In-App and Web (MIAW). Use when the user needs to create, deploy, and activate a messaging channel configured with Omni-Channel Flow, Omni-Channel Queue, User, or Agentforce Service Agent routing. Generates MessagingChannel metadata, deploys it…