mcpField
G
github-outside-sandbox

github-outside-sandbox

github.com/davidondrejDevelopment4.2k75 installsUpdated today
Repository

About github-outside-sandbox

GitHub Outside Sandbox is an agent skill that guides GitHub CLI and Git operations when sandbox restrictions block them. It requires narrow escalation, protects credentials, and verifies results from the host context.

Key features

  1. 01Retries blocked authentication checks outside sandbox
  2. 02Runs required GitHub network operations on host
  3. 03Escalates Git writes only when blocked
  4. 04Avoids token exposure and broad bypasses
  5. 05Verifies repository and GitHub state

Use cases

  1. 01Checking GitHub authentication after sandbox failure
  2. 02Running a blocked pull request or repository operation
  3. 03Pushing changes when Git writes are restricted

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/davidondrej/skills --skill github-outside-sandbox

After installing, type/github-outside-sandboxin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

GitHub Outside Sandbox

  1. Start normally. Escalate only the blocked command and only within the user's authorization.
  2. If sandboxed gh auth status fails, rerun it outside the sandbox before claiming authentication is broken. Never expose or copy tokens.
  3. Run GitHub CLI network operations outside the sandbox when required: gh repo ..., gh pr ..., and related gh commands.
  4. Run Git writes outside the sandbox when .git is outside writable roots or errors mention index.lock or Operation not permitted: git add, git commit, and git push.
  5. Use the harness's official host-execution mechanism. In Codex, set sandbox_permissions: "require_escalated", give a concrete justification, and use only a narrow safe prefix_rule when appropriate.
  6. Never use shell wrappers, credential copying, or broad approval prefixes to bypass the sandbox.
  7. Verify from the host context with git status -sb, git remote -v, and the relevant gh ... view command. Ask the user to authenticate only if the host-context check also fails.

Comments

Markdown supported