Results for “exit-node”

Deno runtime for TypeScript/JavaScript. Covers permissions, standard library, testing, and Deploy. Use for secure, TypeScript-native backend development. USE WHEN: user mentions "deno", "permissions", "Deno.serve", asks about "deno test", "deno deploy", "standard library", "top-level await", "npm compatibility" DO NOT USE FOR: Node.js runtime - use `nodejs` skill instead DO NOT USE FOR: Fresh/Oak frameworks - use framework-specific skills DO NOT USE FOR: Language syntax - use `typescript` skill

Exploit privileged pods, host mounts, runC CVEs, and exposed Docker sockets to break out of a container and reach the underlying host during authorized container-security assessments.

Routes legacy release-manager references to the current runtime capability, preferring matching agents or modern plugin skills.

Rolls back Open-workspace phase or plan commits using a phase manifest with dependency checks and a confirmation gate, preserving history via git revert.

Launches, inspects, and tears down parallel Codex phase fleets in isolated Git worktrees, with explicit approval for bypassing sandbox restrictions.

Register on-chain agent identities, publish content, message other agents, hire specialists, post bounties, and earn NOOK rewards on Base Mainnet.

Scans a codebase for security, database, deployment, code quality, AI/LLM, dependency, frontend, and observability issues before deployment. Intercepts deploy commands and blocks until critical items pass.

`analysis-agent`/`task-agent`/`review-agent`: use for release identity, compatibility, exposure, stop, rollback, or recovery; skip pipeline-only and no-release work.