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-runtimeWrote 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-runtime)<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/tauri-errors-runtime"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/tauri-errors-runtime.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.00097 | $0.03318 |
| Opus 5 | $0.00048 | $0.01659 |
| Sonnet 5 | $0.00019 | $0.00664 |
| Haiku 4.5 | $0.00010 | $0.00332 |
Grade A, and why
tauri-errors-runtime 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 8d 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 — 471 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tauri-errors-runtime
Quick Diagnosis
When a Tauri 2 app crashes or behaves unexpectedly at runtime, identify the error category:
Runtime Error Categories:
1. State panics --> Type mismatch, unmanaged state
2. IPC errors --> Command not found, permission denied, argument mismatch
3. Window errors --> Window/webview not found, already destroyed
4. Plugin errors --> Plugin not initialized, missing permissions
5. Event errors --> Invalid event name, listener leaks
6. Asset errors --> File not found, protocol not configured
7. Panic/crash --> Unhandled panic, thread panic
ALWAYS check the terminal/console output -- Tauri prints panics and errors to stderr.
NEVER ignore unwrap() calls in production code -- they cause panics that crash the app.
Error Lookup Table: State Management
ERR-R001: State type mismatch panic
Error: state not managed for field "state" on command "my_command" or called Option::unwrap() on a None value at runtime.
Cause: The type in State<'_, T> does not match the type passed to manage(). This is a RUNTIME panic, not a compile error.
// WRONG -- register Mutex<Counter>, access as Counter
app.manage(Mutex::new(Counter::default()));
#[tauri::command]
fn bad(state: State<'_, Counter>) { } // PANIC at runtime!
// CORRECT -- types must match exactly
app.manage(Mutex::new(Counter::default()));
#[tauri::command]
fn good(state: State<'_, Mutex<Counter>>) {
let mut counter = state.lock().unwrap();
counter.value += 1;
}
ALWAYS ensure the generic type in State<'_, T> matches exactly what was passed to manage().
ERR-R002: State not registered
Error: state not managed for field "state" -- app panics when the command is first invoked.
Cause: Forgot to call .manage() on the Builder or in setup().
Fix: ALWAYS register state before it is accessed:
tauri::Builder::default()
.manage(AppConfig { api_url: "https://api.example.com".into() })
.manage(Mutex::new(Counter::default()))
// ... state must be registered before commands use it
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.
- 8d ago First seen · 471 lines · 97 tokens per session scan A f35f8f834e33
tauri-errors-runtime is a skill published in the GitHub repository OpenAEC-Foundation/OpenAEC-Workspace-Composer (5 stars, last pushed 5mo ago), licensed MIT. It adds 97 tokens to every session and 3,318 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
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.
schema-validation
JSON/data schema validation for construction data exchange: API payloads, file imports, BIM exports. Ensure data structure compliance before processing.