New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Opencode Sync Sandbox

by iHildy in iHildy/opencode-synced

Sandbox-first workflow for implementing and end to end validating opencode-synced changes.

MITAuto-check passedTesting & QA

Install Opencode Sync Sandbox

skills CLI
$ npx skills add iHildy/opencode-synced --skill opencode-sync-sandbox -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install iHildy/opencode-synced opencode-sync-sandbox --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/iHildy/opencode-synced.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/opencode-sync-sandbox .claude/skills/opencode-sync-sandbox && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
opencode-sync-sandbox
GitHub stars
160
Token cost
~718 tokens
SKILL.md length
300 words
Files
4 (incl. scripts, references)
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Sandbox-first workflow for implementing and end to end validating opencode-synced changes.

  • Works in 7 steps: Create a concrete plan before editing… → Spawn as many subagents as useful for… → Implement the change in small,… → …
  • Making any changes that effect the opencode-synced opencode plugin
  • SKILL.md covers Required Workflow, E2E Reporting Requirements, Sandbox Rules and Upstream Reference Rule, plus 1 more section
  • Runs Shell scripts from its folder; calls bun and python3

What it does

Opencode Sync Sandbox is an agent skill from iHildy/opencode-synced. Sandbox-first workflow for implementing and end to end validating opencode-synced changes. Use when making any changes that effect the opencode-synced opencode plugin. Unless specifically directed not to.

Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/workflow.md`, `scripts/preflight.sh` and `scripts/run-e2e.sh`).

It sits in Testing & QA, covering End-to-end testing. The repository describes itself as: Sync opencode global configurations between machines with a plugin. The licence is MIT.

When your agent uses it

  • Making any changes that effect the opencode-synced opencode plugin
  • Tasks that involve End-to-end testing

Example prompts

  • “/opencode-sync-sandbox”

Requirements

  • Python 3
  • A Bash shell

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Create a concrete plan before editing files.
  2. Spawn as many subagents as useful for parallelizable work (tests, refactors, docs, investigations).
  3. Implement the change in small, reviewable steps.
  4. Add or update unit/regression tests for the behavior you changed.
  5. Run local checks
  6. Run full isolated E2E before declaring success
  7. Report exact evidence: what changed, what tests ran, and an E2E artifact review.

What it can do on your machine

Read from SKILL.md and the folder at commit 0e13dc9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • bun
    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Opencode Sync Sandbox loads about 718 tokens when it runs, and up to ~884 if it reads all its reference files. Until then it costs about 57 tokens; SKILL.md has 300 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~718
With references · SKILL.md plus every file in references/, read only if the agent opens them
~884

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from iHildy/opencode-synced at commit 0e13dc9, republished under its MIT licence (© iHildy). 300 words, ~718 tokens.

Download SKILL.mdSave it as .claude/skills/opencode-sync-sandbox/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
opencode-sync-sandbox
description
Sandbox-first workflow for implementing and end to end validating opencode-synced changes. Use when making any changes that effect the opencode-synced opencode plugin. Unless specifically directed not to.

Opencode Sync Sandbox

Follow this workflow whenever a task changes sync behavior, config handling, command behavior, or repo/GitHub integration.

Required Workflow

  1. Create a concrete plan before editing files.
  2. Spawn as many subagents as useful for parallelizable work (tests, refactors, docs, investigations).
  3. Implement the change in small, reviewable steps.
  4. Add or update unit/regression tests for the behavior you changed.
  5. Run local checks:
    • bun run check
    • bun test
    • bun run build
  6. Run full isolated E2E before declaring success:
    • ./.agents/skills/opencode-sync-sandbox/scripts/run-e2e.sh
    • Run E2E variants that directly exercise the features changed in this task (for example: sessions, secrets, or other changed sync flags/paths).
  7. Report exact evidence: what changed, what tests ran, and an E2E artifact review.

Do not skip E2E for changes that affect sync workflows, path resolution, repo operations, or command execution.

E2E Reporting Requirements

  • Do not report the E2E artifact path unless the user explicitly asks for it.
  • Read results/summary.json, command result payloads under results/, and relevant logs/*.log tails.
  • Summarize the executed flow, pass/fail status, key warnings/errors, and any suspicious signals.
  • If warnings exist, explain whether they are expected, tolerated, or need follow-up.
  • For feature-flagged runs, report the exact artifact-level behavior for each changed feature (including restart requirements when relevant).

Sandbox Rules

  • Keep all E2E state inside .memory/e2e/runs/<run-id>/.
  • Never rely on shared global opencode directories for E2E assertions.
  • Use the harness-created isolated HOME/XDG sandboxes for each instance.
  • Use ephemeral GitHub repos for test runs; keep failed repos only when debugging is needed.

Upstream Reference Rule

Before changing integration-sensitive behavior, inspect upstream opencode source in:

  • .memory/opencode-upstream/opencode

Use this clone to confirm command/server/tool behavior and avoid assumptions.

Helper Scripts

  • Preflight only:
    • ./.agents/skills/opencode-sync-sandbox/scripts/preflight.sh
  • Full two-instance GitHub E2E:
    • ./.agents/skills/opencode-sync-sandbox/scripts/run-e2e.sh
    • Enable secrets coverage: ./.agents/skills/opencode-sync-sandbox/scripts/run-e2e.sh --enable-secrets
    • Enable session database coverage (implies secrets): ./.agents/skills/opencode-sync-sandbox/scripts/run-e2e.sh --enable-sessions

For additional usage flags, run:

  • python3 scripts/e2e/github_two_instance.py --help

© iHildy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in .agents/skills/opencode-sync-sandbox of iHildy/opencode-synced.

  • SKILL.md
  • references/workflow.md
  • scripts/preflight.sh
  • scripts/run-e2e.sh

Open the folder on GitHubat commit 0e13dc9

Compare with similar skills

Opencode Sync Sandbox next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Opencode Sync Sandbox compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Opencode Sync Sandbox this skilliHildy/opencode-synced160—~718Automated safety check: PassMIT
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
Uloop Replay Inputkurotu/VRCQuestTools3733 repos~615Automated safety check: PassMIT
Ui4 Convert Testspayloadcms/payload45k—~3.5kAutomated safety check: PassMIT
E2Estackia/rtp2httpd2.2k—~517Automated safety check: PassGPL-2.0

Similar skills

  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed

  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed

  • Uloop Replay Input

    kurotu/VRCQuestTools

    Replay recorded PlayMode keyboard and mouse input. An agent skill from kurotu/VRCQuestTools.

    373 GitHub starsUsed in 3 repos~615 tokens
    Testing & QAAuto-check passed

  • Ui4 Convert Tests

    payloadcms/payload

    A skill your agent uses when UI changes are complete and e2e tests need updating.

    45k GitHub stars~3.5k tokensUpdated today
    Testing & QAAuto-check passed

  • E2E

    stackia/rtp2httpd

    Write, run, review, or debug rtp2httpd E2E tests and their harness in e2e/ and scripts/run-e2e.sh.

    2.2k GitHub stars~517 tokensUpdated 5 days ago
    Testing & QAAuto-check passed

  • Moav E2E

    MotherofallVPNs/MoaV

    Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.

    448 GitHub stars~1.9k tokensUpdated yesterday
    Testing & QAAuto-check: notes

Categories

Questions about Opencode Sync Sandbox

What does Opencode Sync Sandbox do?

Sandbox-first workflow for implementing and end to end validating opencode-synced changes. Opencode Sync Sandbox is an agent skill from iHildy/opencode-synced. Sandbox-first workflow for implementing and end to end validating opencode-synced changes.

When should I use Opencode Sync Sandbox?

Opencode Sync Sandbox fits situations like: making any changes that effect the opencode-synced opencode plugin; tasks that involve End-to-end testing.

How do I install Opencode Sync Sandbox in Claude Code?

Run `npx skills add iHildy/opencode-synced --skill opencode-sync-sandbox -a claude-code`. Or copy the skill folder (.agents/skills/opencode-sync-sandbox in iHildy/opencode-synced) into .claude/skills/opencode-sync-sandbox in your project. Claude Code loads it when a task matches its description.

How do I install Opencode Sync Sandbox in Codex?

Run `npx skills add iHildy/opencode-synced --skill opencode-sync-sandbox -a codex`. Or copy the skill folder (.agents/skills/opencode-sync-sandbox in iHildy/opencode-synced) into .agents/skills/opencode-sync-sandbox in your project. Codex loads it when a task matches its description.

Can I use Opencode Sync Sandbox in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add iHildy/opencode-synced --skill opencode-sync-sandbox -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/opencode-sync-sandbox, .gemini/skills/opencode-sync-sandbox, .github/skills/opencode-sync-sandbox and .opencode/skills/opencode-sync-sandbox in your project.

What does Opencode Sync Sandbox need to run?

Going by SKILL.md and its folder, Opencode Sync Sandbox needs a shell for the scripts in its folder and the command-line tools its instructions call (bun and python3). Our summary lists: Python 3; A Bash shell.

Does Opencode Sync Sandbox access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Opencode Sync Sandbox safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Opencode Sync Sandbox use?

Opencode Sync Sandbox is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Opencode Sync Sandbox use?

About 718 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 166 tokens, read only when the agent opens those files.

What are the alternatives to Opencode Sync Sandbox?

Skills that share tags, products or a category with Opencode Sync Sandbox: Web Application Testing (anthropics/skills, 180k stars), TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), Uloop Replay Input (kurotu/VRCQuestTools, 373 stars) and Ui4 Convert Tests (payloadcms/payload, 45k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Opencode Sync Sandbox?

iHildy (a GitHub user) maintains it in iHildy/opencode-synced, which has 160 GitHub stars. The repository was last updated on September 23, 2026.

Source: iHildy/opencode-synced on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.