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-build-deploygit 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-build-deploy)<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/tauri-impl-build-deploy"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/tauri-impl-build-deploy/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-build-deploy"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/tauri-impl-build-deploy.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.00119 | $0.02847 |
| Opus 5 | $0.00060 | $0.01424 |
| Sonnet 5 | $0.00024 | $0.00569 |
| Haiku 4.5 | $0.00012 | $0.00285 |
Grade B, and why
tauri-impl-build-deploy scanned grade B with 1 finding 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 10d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt-get update How it starts
The opening of the file, as written. The whole thing — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tauri-impl-build-deploy
Quick Reference
Build Commands
| Command | Purpose |
|---|---|
tauri build |
Full production build with bundling |
tauri build --no-bundle |
Compile only, skip installers |
tauri bundle --bundles app,dmg |
Bundle specific formats only |
tauri bundle --config src-tauri/tauri.appstore.conf.json |
Build with alternate config |
tauri android build |
Android production build |
tauri ios build |
iOS production build |
Platform Bundler Formats
| Platform | Formats | Notes |
|---|---|---|
| Windows | NSIS installer, MSI (WiX), portable exe | WebView2 install mode configurable |
| macOS | App bundle (.app), DMG | Code signing + notarization required for distribution |
| Linux | AppImage, .deb, .rpm, Snap, Flatpak | AppImage is the most universal |
| Android | APK, AAB | Play Store requires AAB |
| iOS | IPA | App Store or TestFlight distribution |
Critical Warnings
NEVER lose the updater private key -- it is impossible to push updates to existing installations without it. Back it up securely.
NEVER set createUpdaterArtifacts: true without setting the TAURI_SIGNING_PRIVATE_KEY environment variable -- the build will fail.
NEVER distribute unsigned macOS builds -- Gatekeeper quarantines them. Use at minimum ad-hoc signing ("-").
NEVER use "v1Compatible" for createUpdaterArtifacts in new projects -- only for migrating from v1 updater.
ALWAYS commit src-tauri/Cargo.lock for deterministic builds across environments.
ALWAYS set GitHub token permissions to "Read and write" when using tauri-action for releases.
Essential Patterns
Pattern 1: Bundle Configuration
The bundle section in tauri.conf.json controls all packaging:
{
"bundle": {
"active": true,
"targets": "all",
"icon": [
"icons/32x32.png",
"icons/128x128.png",
"icons/[email protected]",
"icons/icon.icns",
"icons/icon.ico"
],
"identifier": "com.example.myapp",
"resources": {
"models/": "models/",
"config.toml": "config.toml"
},
"externalBin": ["binaries/ffmpeg"],
"category": "Utility",
"copyright": "Copyright 2026 Example Inc.",
"publisher": "Example Inc.",
"license": "MIT",
"createUpdaterArtifacts": true
}
}
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.
- 10d ago First seen · 400 lines · 119 tokens per session scan B 98c95044d89b
tauri-impl-build-deploy is a skill published in the GitHub repository OpenAEC-Foundation/OpenAEC-Workspace-Composer (5 stars, last pushed 5mo ago), licensed MIT. It adds 119 tokens to every session and 2,847 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
app-release
Use when the user asks to release a new version, ship a build, or publish a Skill Zoo release. Also use when a tag push results in Homebrew 404 errors or missing artifact failures.
npm-release
Use when publishing or preparing to publish an npm package from this repository, especially the Skill Zoo CLI package under packages/cli. Also use when npm publish fails because of duplicate versions, npm authentication, browser authentication, dist-tag propagation, tarball contents, bin entry issues, or…
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
release-app
Cut a workhub release — bump the app version, write the changelog entry, commit to main, tag vX.Y.Z, push, and verify the GitHub Release published with every required asset. Use when the user wants to release or ship the workhub app, tag a version, or publish a build.
create-release-notes
Write user-facing release notes from the Conventional Commits history between two refs — grouped by impact, in plain language, with internal-only changes filtered out. Use when the user wants release notes, an announcement of what's new in a version, or a user-readable summary of changes since the last release…
git-release-manager
Use when the user explicitly asks to prepare, tag, publish, push, or audit a Git release. Inspect branch, worktree, version metadata, changelog, tests, and release artifacts first, obtain confirmation for irreversible release actions, and record a recovery path.