code-mode-porting

Name: code-mode-porting
Availability: InStock
Author: TinNguyen

Port a workspace gateway architecture with discovery-first tooling and sandboxed execution.

1|Updated Jan 26, 2026

Search Tags:#sandboxing #tool-discovery #code-mode #porting #gateway-architecture #workspace-gateway #policy-boundary

Ready to run

npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill code-mode-porting

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-mode-porting
Source: https://github.com/AskTinNguyen/vesper-team-skills/tree/main/code-mode-porting
Command: npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill code-mode-porting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Port Vesper's bundled workspace gateway architecture as a reusable pattern, not as a literal copy. The goal is to give another agent app:

one primary workspace gateway
lightweight tool discovery
host-owned side effects
sandboxed execution
clear policy and retry semantics

Core Features & Use Cases

One primary workspace gateway enabling discovery-first tool exposure
Lightweight catalog-driven discovery for tools and packs
Host-owned privileged execution boundary with sandboxed workers
Clear policy boundary and retry semantics at execution time
Guidance for porting architecture to other agent apps and runtimes

Quick Start

Port code-mode gateway architecture into another app by establishing a single workspace gateway with discovery-first tooling, sandboxed execution, and a host-owned boundary

Frequently Asked Questions about code-mode-porting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up a workspace gateway with sandboxed execution and tool discovery?▼

You port the architecture by establishing a single primary workspace gateway that provides catalog-driven tool discovery and enforces a sandbox boundary for host-owned side effects. It requires a host dispatcher and a policy boundary to manage execution.

What is a discovery-first tooling gateway and when do I need one for my agent app?▼

A discovery-first tooling gateway is a single primary surface that uses a lightweight catalog to expose tools and packs to an agent app. You need this pattern when you want host-owned privileged execution boundaries with sandboxed workers and clear retry semantics.

Can I port a code-mode gateway architecture into any agent runtime?▼

Yes, the code-mode gateway architecture is designed to be ported as a reusable pattern into other agent apps and runtimes. It requires establishing a single gateway surface, catalog-driven discovery, a host dispatcher, and a policy boundary to manage execution.

Does a workspace gateway pattern support host-owned side effects and retry semantics?▼

Yes, the workspace gateway pattern explicitly provides host-owned privileged execution boundaries with clear policy and retry semantics at execution time. The host dispatcher manages these side effects safely within the sandbox boundary.

What are the limitations of using a single gateway surface for tool discovery and execution?▼

The main limitation is the strict requirement for a policy boundary and a host dispatcher to manage execution safely. Without proper sandbox boundary enforcement, the single gateway surface cannot guarantee safe host-owned side effects or proper tool discovery.