Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/OpenAEC-Foundation/OpenAEC-Workspace-Composernpx agentmods add skills/openaec-foundation/openaec-workspace-composer/tauri-errors-permissionsWrote 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-errors-permissions)<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/tauri-errors-permissions"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/tauri-errors-permissions/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-errors-permissions"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/tauri-errors-permissions.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.00082 | $0.03344 |
| Opus 5 | $0.00041 | $0.01672 |
| Sonnet 5 | $0.00016 | $0.00669 |
| Haiku 4.5 | $0.00008 | $0.00334 |
Grade A, and why
tauri-errors-permissions 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 12d 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 — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tauri-errors-permissions
Diagnostic Decision Tree
Permission-related error in Tauri 2
|
+-- Error: "command <name> not allowed"
| |
| +-- Plugin command (e.g., fs, http, dialog)?
| | --> Section 1: Missing Plugin Permissions
| |
| +-- Custom #[tauri::command]?
| | --> Section 2: Custom Command Permissions
| |
| +-- Core feature (window, event, path, menu, tray)?
| --> Section 3: Core Permissions
|
+-- Error: CSP violation (console shows "Refused to ...")
| --> Section 4: CSP Violations
|
+-- Error: scope violation / path access denied
| --> Section 5: Scope Violations
|
+-- No error but feature silently does nothing
| --> Section 6: Silent Permission Failures
|
+-- Build error related to permissions / capabilities
| --> Section 7: Configuration Format Errors
Section 1: Missing Plugin Permissions
Symptoms
- Runtime error:
command <plugin>|<command> not allowed - Plugin API call throws immediately after
invoke() - Works in dev but fails in production (or vice versa)
Debugging Workflow
Step 1.1: Verify the plugin is registered in Rust (src-tauri/src/lib.rs):
tauri::Builder::default()
.plugin(tauri_plugin_fs::init()) // REQUIRED for each plugin
.plugin(tauri_plugin_dialog::init())
.plugin(tauri_plugin_http::init())
Step 1.2: Verify permissions exist in a capability file. Check src-tauri/capabilities/default.json:
{
"$schema": "../gen/schemas/desktop-schema.json",
"identifier": "default",
"windows": ["main"],
"permissions": [
"core:default",
"fs:default",
"dialog:default",
"http:default"
]
}
Step 1.3: Verify the specific command is covered. <plugin>:default grants a safe subset. Some commands require explicit permission:
| Plugin | Commands NOT in :default |
Required Permission |
|---|---|---|
fs |
write operations | fs:allow-write-file, fs:allow-mkdir, fs:allow-remove |
shell |
execute, spawn | shell:allow-execute, shell:allow-spawn |
clipboard-manager |
all operations | clipboard-manager:allow-read-text, clipboard-manager:allow-write-text |
http |
requests to URLs | Requires URL scope configuration |
notification |
request-permission | notification:allow-request-permission |
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.
- 12d ago First seen · 418 lines · 82 tokens per session scan A 1363e3fa016e
tauri-errors-permissions is a skill published in the GitHub repository OpenAEC-Foundation/OpenAEC-Workspace-Composer (5 stars, last pushed 5mo ago), licensed MIT. It adds 82 tokens to every session and 3,344 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
aios-arch-health
Deterministic architecture-health governance for repositories. Use when a project needs complexity, duplication, dependency, test, coverage, mutation, QA, performance, database, concurrency, or failure-injection evidence; evidence provenance and artifact digests; protected specification, test, quality-profile, or QA…
aios-exec
A controlled workflow for carrying out clearly defined changes and checks in a project workspace. It covers code, bug fixes, documentation, scripts, tests, linting, type checks, builds, interface changes, and deployment preparation.
ha-logs
A read-only troubleshooting skill for querying Hope Agent’s local SQLite databases, which store logs, conversations, and background-job status.
ha-self-diagnosis
Self-understanding and issue reporting for Hope Agent itself. Use when the user asks how Hope Agent works internally, asks about its own source code/docs/runtime behavior, reports a bug/failure/slowness/crash, asks to diagnose logs, or asks to create/submit a GitHub issue for a bug, feature request, or improvement…
ha-debug
Hope-native debugging for code failures, regressions, crashes, flaky behavior, and bad output: reproduce or characterize, rank falsifiable hypotheses, fix the smallest root cause, and prove the failing path.
bim-validation-pipeline
Build automated BIM validation pipelines for IFC/Revit data. Continuous validation against IDS, LOD requirements, COBie, and project-specific BEP standards.