Skill

sandbox-security

Daytona sandbox security. Use for token handling, credential security, full paths in SSH.

Install

npx claudepluginhub spences10/ralph-town --plugin ralph-town

Tool Access

This skill uses the workspace's default tool permissions.

Preview

SSH sessions have broken PATH. ALWAYS use full paths:

Supporting Assets

references/security-details.md

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

169.2k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

169.2k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

169.2k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitJan 31, 2026

Actions

View Source View Plugin View on GitHub View README

Sandbox Security

Full Paths Required

SSH sessions have broken PATH. ALWAYS use full paths:

Tool

Path

git

/usr/bin/git

/usr/bin/gh

bun

/root/.bun/bin/bun

ls/cat/echo

/bin/ls, /bin/cat, /bin/echo

Token Handling

NEVER embed tokens in URLs - they leak to process list, logs, errors.

# BAD - token visible in ps, logs, error messages /usr/bin/git clone https://$GH_TOKEN@github.com/owner/repo.git # GOOD - use credential helper /usr/bin/git config --global credential.helper store /bin/echo "https://oauth2:$GH_TOKEN@github.com" > ~/.git-credentials /bin/chmod 600 ~/.git-credentials /usr/bin/git clone https://github.com/owner/repo.git

Env Var Visibility

Env vars via --env are visible to ALL processes in sandbox:

env command lists everything

/proc/*/environ exposes all process env vars

Any script/binary can read $GH_TOKEN

Mitigations:

Only pass credentials the sandbox legitimately needs

Use short-lived, minimally-scoped tokens

Delete sandbox promptly after use

SSH Credential Setup

Team-lead configures credentials BEFORE spawning teammate:

# $GH_TOKEN expands LOCALLY (double quotes!) ssh <token>@ssh.app.daytona.io " /usr/bin/git config --global credential.helper store && /bin/echo 'https://oauth2:$GH_TOKEN@github.com' > ~/.git-credentials && /bin/chmod 600 ~/.git-credentials "

Reference Files