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-testinggit 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-testing)<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/tauri-impl-testing"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/tauri-impl-testing/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-testing"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/tauri-impl-testing.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.00103 | $0.02936 |
| Opus 5 | $0.00051 | $0.01468 |
| Sonnet 5 | $0.00021 | $0.00587 |
| Haiku 4.5 | $0.00010 | $0.00294 |
Grade A, and why
tauri-impl-testing 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 — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tauri-impl-testing
Quick Reference
Testing Layers
| Layer | Tool | What It Tests |
|---|---|---|
| Rust Unit Tests | cargo test |
Command logic, state management, error handling |
| Frontend Unit Tests | Vitest / Jest + @tauri-apps/api/mocks |
UI components, IPC call handling |
| Integration Tests | Vitest / Jest + mockIPC | Frontend-backend contract |
| E2E Tests | WebDriver (Selenium/Playwright) | Full application behavior |
Mock API Imports
import { mockIPC, mockWindows, mockConvertFileSrc, clearMocks } from '@tauri-apps/api/mocks';
Mock Functions
| Function | Purpose | Scope |
|---|---|---|
mockIPC(handler, options?) |
Intercept invoke() calls |
All commands |
mockWindows(current, ...rest) |
Mock window labels | Window API |
mockConvertFileSrc(platform) |
Mock file-to-URL conversion | Asset protocol |
clearMocks() |
Remove all mocks | All |
Critical Warnings
ALWAYS call clearMocks() in afterEach() -- failing to do so leaks mocks between tests, causing flaky test results.
NEVER test Tauri commands by running them through IPC in unit tests -- test the underlying Rust function directly. Commands are regular functions.
NEVER import @tauri-apps/api modules in test files without mocking first -- they throw errors outside a Tauri webview context.
ALWAYS use mockIPC before any invoke() call in frontend tests -- without it, invoke() attempts to use the actual IPC bridge which does not exist in a test environment.
NEVER forget to handle the Promise<UnlistenFn> return type when testing event listeners -- listen() returns a Promise, not a synchronous function.
Essential Patterns
Pattern 1: Rust Unit Testing (Commands Are Regular Functions)
Tauri commands decorated with #[tauri::command] are plain Rust functions. Test them directly without any Tauri runtime:
// src-tauri/src/commands.rs
#[tauri::command]
pub fn greet(name: String) -> String {
format!("Hello, {}!", name)
}
#[tauri::command]
pub fn add(a: i32, b: i32) -> i32 {
a + b
}
#[cfg(test)]
mod tests {
use super::*;
#[test]
fn test_greet() {
let result = greet("World".to_string());
assert_eq!(result, "Hello, World!");
}
#[test]
fn test_add() {
assert_eq!(add(2, 3), 5);
assert_eq!(add(-1, 1), 0);
}
}
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 · 448 lines · 103 tokens per session scan A faa326cd5bf3
tauri-impl-testing is a skill published in the GitHub repository OpenAEC-Foundation/OpenAEC-Workspace-Composer (5 stars, last pushed 5mo ago), licensed MIT. It adds 103 tokens to every session and 2,936 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
performance-engineer
Becomes a senior performance engineer who identifies bottlenecks, designs optimization strategies, and conducts load testing using systematic profiling and benchmarking methodology. Use when the user needs performance analysis, load testing, bottleneck identification, latency optimization, or capacity planning. Do NOT…
qa
QA testing skill with real browser automation. Use when asked to "test this site", "QA this page", "check for visual bugs", "verify the deploy", or when Hydra needs browser validation for UI changes. Requires the browse binary.
aios-prompt-compare
An internal testing workflow for comparing prompts and coding-agent skills on the same input. It compares a weak prompt, a reusable stronger prompt, and the result from a real skill, while preserving the original outputs.
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…
cc-port-live-e2e
Run and audit CC Port's opt-in live Windows package E2E and broader native remaining-scope validation. Use when validating that a packaged installer or release candidate can enable AI automation, upload/download a harmless Skill through packaged MCP plus desktop approval, verify Registry v1 and Git blob bytes, or when…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.