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-errors-ipcgit 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-errors-ipc)<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/tauri-errors-ipc"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/tauri-errors-ipc/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-ipc"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/tauri-errors-ipc.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.03204 |
| Opus 5 | $0.00047 | $0.01602 |
| Sonnet 5 | $0.00019 | $0.00641 |
| Haiku 4.5 | $0.00009 | $0.00320 |
Grade A, and why
tauri-errors-ipc 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 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.
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 — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tauri-errors-ipc
Diagnostic Decision Tree
invoke() fails or returns unexpected result
|
+-- Error: "command <name> not found"
| --> Step 1: Command Registration (Section 1)
|
+-- Error: "command <name> not allowed"
| --> Permission issue. See tauri-errors-permissions skill.
|
+-- Error contains "invalid type" / "missing field" / "invalid value"
| --> Step 2: Serialization & Type Mismatch (Section 2)
|
+-- Error: invoke returns string instead of object (or vice versa)
| --> Step 3: Error Serialization Pattern (Section 3)
|
+-- Rust panics (app crashes, no error returned to JS)
| --> Step 4: Async Command Panics (Section 4)
|
+-- Error caught but message is unhelpful ("null" or empty string)
| --> Step 5: Structured Error Pattern (Section 5)
|
+-- No error, but invoke never resolves (hangs forever)
| --> Step 6: Deadlocks & Blocking (Section 6)
Section 1: Command Not Found
Symptoms
- JavaScript error:
command <name> not found invoke('my_command')rejects immediately
Debugging Steps
Step 1.1: Verify the command is registered in generate_handler![]:
// src-tauri/src/lib.rs
tauri::Builder::default()
.invoke_handler(tauri::generate_handler![
my_command, // Direct function
commands::my_command, // Module-prefixed function
])
Step 1.2: Verify there is only ONE invoke_handler() call. Multiple calls do NOT merge -- only the last one takes effect:
// WRONG: first handler is silently overwritten
builder
.invoke_handler(tauri::generate_handler![cmd_a])
.invoke_handler(tauri::generate_handler![cmd_b]) // Only this one works
Step 1.3: Verify the function has the #[tauri::command] attribute:
#[tauri::command] // REQUIRED -- without this, generate_handler! will fail to compile
fn my_command() -> String {
"hello".into()
}
Step 1.4: Verify the command name matches. Rust uses snake_case function names. The frontend calls the same snake_case name:
// Command: fn get_user_data() -> ...
await invoke('get_user_data'); // CORRECT: snake_case
await invoke('getUserData'); // WRONG: command names are NOT auto-converted
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 · 427 lines · 94 tokens per session scan A 0690b7094535
tauri-errors-ipc 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,204 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
schema-validation
JSON/data schema validation for construction data exchange: API payloads, file imports, BIM exports. Ensure data structure compliance before processing.
interoperability-analyzer
Analyze data interoperability issues in construction projects. Identify format incompatibilities and data loss points.
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.
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…
n8n-errors-connection
Use when troubleshooting API connection failures, credential errors, or timeout issues in n8n. Prevents misdiagnosis by providing deterministic symptom-cause-fix tables. Covers API failures, credential errors, timeout configuration, SSL/TLS issues, webhook URL problems (test vs production), rate limiting, queue mode…
rest-graphql-debug
Debug REST/GraphQL APIs: status codes, auth, schemas, repro.