wasm-agent
Create and manage sandboxed WASM agents for isolated code execution
- License 许可
- MIT
- 最近更新
- 2026-10-08
- Stars
- ★ 11
- Forks
- 3
01 前言 Front Matter
- name
- wasm-agent
- description
- Create and manage sandboxed WASM agents for isolated code execution
- allowed-tools
- mcp__plugin_ruflo-core_ruflo__wasm_agent_create mcp__plugin_ruflo-core_ruflo__wasm_agent_list mcp__plugin_ruflo-core_ruflo__wasm_agent_prompt mcp__plugin_ruflo-core_ruflo__wasm_agent_tool mcp__plugin_ruflo-core_ruflo__wasm_agent_files mcp__plugin_ruflo-core_ruflo__wasm_agent_export mcp__plugin_ruflo-core_ruflo__wasm_agent_terminate Bash
- argument-hint
- <create|list|prompt|terminate> [options]
03 SKILL.md 正文
WASM Agent
Create sandboxed agents that run in WebAssembly for safe, isolated execution.
When to use
When you need to run untrusted code, experiment with agent configurations, or create portable agents that run anywhere WASM is supported.
Steps
- Create agent — call
mcp__plugin_ruflo-core_ruflo__wasm_agent_createwith agent configuration - Send prompt — call
mcp__plugin_ruflo-core_ruflo__wasm_agent_promptto interact with the agent - Use tools — call
mcp__plugin_ruflo-core_ruflo__wasm_agent_toolto give the agent access to specific tools - Manage files — call
mcp__plugin_ruflo-core_ruflo__wasm_agent_filesto read/write files in the sandbox - Export — call
mcp__plugin_ruflo-core_ruflo__wasm_agent_exportto package the agent for sharing - List agents — call
mcp__plugin_ruflo-core_ruflo__wasm_agent_listto see all running WASM agents - Terminate — call
mcp__plugin_ruflo-core_ruflo__wasm_agent_terminateto stop an agent
Benefits
- Full sandbox isolation — agents cannot access the host filesystem
- Portable — export and run on any WASM runtime
- Reproducible — same behavior across platforms
- Safe — no risk of system damage from agent actions
04 同仓库更多 Skills
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration).
chrome-cdp
Drive a real Chrome via the Chrome DevTools Protocol (CDP). Ensures a debuggable Chrome is running (launching it if needed) so the agent can navigate, read page content, inspect the DOM, run JavaScript, and take screenshots — without the user typing any launch command. Includes a first-class "review a live running app" flow: point Chrome at the app under development and inspect/screenshot the REAL page (what a static-artifact tool cannot do). Backed by Glimpse and the chrome-devtools MCP server. Use when asked to "use chrome", "open chrome", "drive my browser", "read the page in chrome", "review the running app", "screenshot the app", or "/chrome-cdp".
check-identity-pack
Run an AFP 100-point or AUSTRAC safe-harbour identity check over a set of documents, and report exactly what's missing. Use when the user asks to check identity documents, verify someone's ID for onboarding, or assess whether a document pack satisfies Australian identity requirements.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
cellxgene-census
Query the CZ CELLxGENE Census programmatically for versioned public single-cell and spatial transcriptomics data. Use when you need population-scale cell metadata, gene expression slices, Census summary counts, source H5AD URIs/downloads, embeddings, spatial Census data, or reference atlas comparisons across organisms, tissues, diseases, assays, and cell types. For analyzing your own local single-cell data use scanpy, anndata, or scvi-tools.