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-impl-plugin-developmentgit 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-impl-plugin-development)<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/tauri-impl-plugin-development"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/tauri-impl-plugin-development/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-impl-plugin-development"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/tauri-impl-plugin-development.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.00087 | $0.02091 |
| Opus 5 | $0.00044 | $0.01045 |
| Sonnet 5 | $0.00017 | $0.00418 |
| Haiku 4.5 | $0.00009 | $0.00209 |
Grade A, and why
tauri-impl-plugin-development 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 9d 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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tauri-impl-plugin-development
Quick Reference
Plugin Builder API
| Method | Purpose | Example |
|---|---|---|
Builder::new("name") |
Create plugin builder | Builder::new("my-plugin") |
.invoke_handler() |
Register plugin commands | .invoke_handler(generate_handler![cmd]) |
.setup() |
Plugin initialization hook | .setup(|app, api| { Ok(()) }) |
.on_event() |
App event handler | .on_event(|app, event| { }) |
.on_navigation() |
Webview navigation filter | .on_navigation(|window, url| true) |
.on_webview_ready() |
Webview ready hook | .on_webview_ready(|window| { }) |
.on_drop() |
Plugin cleanup hook | .on_drop(|app| { }) |
.build() |
Finalize and return TauriPlugin | .build() |
Plugin Command Invocation (Frontend)
| Pattern | Example |
|---|---|
| Command prefix | plugin:<name>|<command> |
| JS invoke call | invoke('plugin:my-plugin|do_something', { arg: 'value' }) |
Plugin Permission Generation
| Item | Description |
|---|---|
build.rs location |
Plugin crate root |
| Command list | const COMMANDS: &[&str] = &["cmd_a", "cmd_b"]; |
| Builder call | tauri_plugin::Builder::new(COMMANDS).build(); |
| Generated permissions | allow-cmd-a, deny-cmd-a, allow-cmd-b, deny-cmd-b |
Critical Warnings
NEVER use multiple .invoke_handler() calls on the app Builder -- only the last one takes effect. Plugin commands use their own .invoke_handler() on the plugin Builder.
NEVER forget the R: Runtime generic on plugin command functions -- plugin commands MUST use <R: Runtime> to remain runtime-agnostic.
NEVER register plugin state on the app Builder -- use app.manage() inside the plugin's .setup() hook.
NEVER skip build.rs permission generation -- without it, plugin commands will fail with "command not allowed" at runtime.
ALWAYS use the plugin:<name>|<command> prefix when invoking plugin commands from JavaScript.
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.
- 9d ago First seen · 304 lines · 87 tokens per session scan A 493d785d5878
tauri-impl-plugin-development is a skill published in the GitHub repository OpenAEC-Foundation/OpenAEC-Workspace-Composer (5 stars, last pushed 5mo ago), licensed MIT. It adds 87 tokens to every session and 2,091 once invoked, about $0.0004 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
massing-bim
Drive a Massing BIM/AEC project from an AI agent over MCP — read a project's status, records, CDE, KPI and model-quality checks; run standards-compliance, schedule-risk, embodied-carbon, permit- readiness and drawing-QA analyses; author the IFC model with GUID-stable recipes; and draft RFIs. Use when the user asks to…
ara3d-sdk
Use when processing AEC/BIM 3D data in .NET 8 — mesh generation and transformation, SIMD-accelerated math, IFC/STEP/PLY to glTF/GLB/VIM conversion, plugin development. Ara3D-SDK: high-performance .NET 3D geometry and BIM library suite.
elements
Use when generating building information models (BIM) programmatically in C#/.NET — wall, beam, column, floor creation, geometry kernel (BREP/CSG), glTF/IFC/JSON serialization, MEP systems, spatial grids. Hypar Elements: the smallest useful BIM — a cross-platform C# library for creating building elements without…
3d-skills
Use when working with 3D Gaussian Splatting (3DGS), .ply model cleanup/compression/publishing, interactive 360-degree panorama visualization and virtual tours, AEC/BIM 3D data processing, or CSG solid modeling. Index of 5 skills: SuperSplat, Photo-Sphere-Viewer, Ara3D-SDK, Elements, and OpenCSG.NET.
aios-arch
A workflow for reviewing software architecture, including service boundaries, technical choices, data and model boundaries, AI workflows, reliability, and long-term complexity.
aios-product
A product-management workflow for turning an approved direction into a defined software version with a product brief, priorities, acceptance measures, pilot or user-acceptance testing, and handover details.