@kokorolx/ai-sandbox-wrapper 3.4.3 → 4.0.1

package/dockerfiles/opencode/Dockerfile

@@ -1,9 +0,0 @@
-FROM ai-base:latest
-
-USER root
-RUN curl -fsSL https://opencode.ai/install | bash && \
-    mv /home/agent/.opencode/bin/opencode /usr/local/bin/opencode && \
-    rm -rf /home/agent/.opencode
-
-USER agent
-ENTRYPOINT ["opencode"]

package/dockerfiles/sandbox/skills/rtk/SKILL.md

@@ -1,103 +0,0 @@
----
-name: rtk
-description: "Token optimizer for AI coding agents. Wraps common CLI commands with rtk to reduce LLM token consumption by 60-90%."
-compatibility: "OpenCode with RTK binary installed"
-metadata:
-  author: Sisyphus
-  version: "1.0.0"
----
-
-# RTK — Rust Token Killer
-
-**Purpose**: Reduce token consumption by 60-90% on shell commands. RTK filters and compresses command output before it reaches your context.
-
-## When This Skill Activates
-
-This skill is loaded automatically. Once active, **always** prefix supported commands with `rtk`.
-
-## Command Mappings (MANDATORY)
-
-When running shell commands via Bash tool, use `rtk` prefix for these commands:
-
-| Instead of | Use | Savings |
-|-----------|-----|---------|
-| `git status` | `rtk git status` | ~80% |
-| `git diff` | `rtk git diff` | ~75% |
-| `git log` | `rtk git log` | ~80% |
-| `git add/commit/push/pull` | `rtk git add/commit/push/pull` | ~90% |
-| `ls` / `ls -la` | `rtk ls` | ~80% |
-| `cat file` | `rtk read file` | ~70% |
-| `grep pattern .` | `rtk grep pattern .` | ~80% |
-| `rg pattern` | `rtk grep pattern .` | ~80% |
-| `npm test` / `cargo test` / `pytest` | `rtk test <cmd>` | ~90% |
-| `npm run build` / `cargo build` | `rtk err <cmd>` | ~80% |
-| `gh pr list/view` | `rtk gh pr list/view` | ~70% |
-| `docker ps` | `rtk docker ps` | ~80% |
-| `eslint` / `tsc` | `rtk lint` / `rtk tsc` | ~80% |
-
-## Searching Inside `node_modules` / Ignored Directories
-
-By default, `rtk grep` respects `.gitignore` rules — meaning `node_modules`, `.nuxt`, `dist`, etc. are **excluded**. This is the right behavior 99% of the time.
-
-When you **need** to search inside ignored directories (debugging a library, checking an API signature, tracing a dependency bug):
-
-```bash
-# Search all files including node_modules (--no-ignore bypasses .gitignore)
-rtk grep "defineStore" . --no-ignore
-
-# Search a specific package only (combine --no-ignore with --glob)
-rtk grep "defineStore" . --no-ignore --glob 'node_modules/pinia/**'
-```
-
-**What does NOT work:**
-- `rtk grep "pattern" node_modules/pinia/` — still excluded even with direct path
-- `rtk grep "pattern" . --glob 'node_modules/**'` — glob alone doesn't override .gitignore
-
-**Key flag: `--no-ignore`** — this is the ONLY way to search ignored directories with rtk grep.
-
-### Other useful `rtk grep` flags
-
-```bash
-rtk grep "pattern" . -t ts          # Filter by file type (ts, py, rust, etc.)
-rtk grep "pattern" . -m 100         # Increase max results (default: 50)
-rtk grep "pattern" . -u             # Ultra-compact mode (even fewer tokens)
-rtk grep "pattern" . -l 120         # Max line length before truncation (default: 80)
-```
-
-## Commands to NOT Wrap
-
-Do NOT prefix these with `rtk` (unsupported or counterproductive):
-
-- `npx`, `npm install`, `pip install` (package managers)
-- `node`, `python3`, `ruby` (interpreters)
-- `nano-brain`, `openspec`, `opencode` (custom tools)
-- Heredocs (`<<EOF`)
-- Piped commands (`cmd1 | cmd2`) — wrap only the first command if applicable
-- Commands already prefixed with `rtk`
-
-## How RTK Works
-
-```
-Without RTK:  git status → 50 lines raw output → 2,000 tokens
-With RTK:     rtk git status → "3 modified, 1 untracked ✓" → 200 tokens
-```
-
-RTK runs the real command, then filters/compresses the output. The agent sees a compact summary instead of verbose raw output.
-
-## Detection
-
-Before using RTK commands, verify it's installed:
-```bash
-rtk --version
-```
-
-If `rtk` is not found, skip this skill — run commands normally without the `rtk` prefix.
-
-## Token Savings Reference
-
-Typical 30-min coding session:
-- Without RTK: ~150,000 tokens
-- With RTK: ~45,000 tokens
-- **Savings: ~70%**
-
-Biggest wins: test output (`rtk test` — 90%), git operations (`rtk git` — 80%), file reading (`rtk read` — 70%).

package/dockerfiles/sandbox/skills/rtk-setup/SKILL.md

@@ -1,118 +0,0 @@
----
-name: rtk-setup
-description: "One-time setup + ongoing enforcement of RTK (Rust Token Killer) across sessions and subagents. Persists RTK instructions to AGENTS.md and propagates to delegated tasks."
-compatibility: "OpenCode with RTK binary installed"
-metadata:
-  author: Sisyphus
-  version: "1.0.0"
----
-
-# RTK Setup — Persistent RTK Enforcement
-
-This skill performs **setup** (persist RTK instructions) and **ongoing enforcement** (use rtk, propagate to subagents).
-
-## Phase 1: Detection (ALWAYS run first)
-
-Run these checks before anything else:
-
-```bash
-rtk --version
-```
-
-- If `rtk` is NOT found → **STOP**. Tell the user: "RTK is not installed. Install it first: `cargo install --git https://github.com/rtk-ai/rtk --locked`". Do NOT proceed with setup.
-- If `rtk` IS found → continue.
-
-### Check oh-my-opencode
-
-```bash
-ls ~/.config/opencode/oh-my-opencode.json 2>/dev/null
-```
-
-- If found → omo is installed. Note this for Phase 2.
-- If not found → skip omo-specific steps.
-
-## Phase 2: Setup (persist to AGENTS.md)
-
-Check BOTH of these files for the RTK managed block:
-
-1. **User-level**: `~/.config/opencode/AGENTS.md`
-2. **Project-level**: `./AGENTS.md` (current workspace)
-
-For EACH file, check if `<!-- RTK:START -->` exists. If it does NOT exist, **append** the following managed block to the file (create the file if it doesn't exist). NEVER replace existing content — only append.
-
-```markdown
-<!-- RTK:START -->
-<!-- Managed block - do not edit manually. Updated by: rtk-setup skill -->
-
-## RTK Token Optimizer
-
-This project uses **RTK** (Rust Token Killer) to reduce LLM token consumption by 60-90%.
-
-### Rules for ALL agents (including subagents)
-
-**ALWAYS** prefix these commands with `rtk`:
-
-| Command | Use instead |
-|---------|-------------|
-| `git status/diff/log/add/commit/push/pull` | `rtk git ...` |
-| `ls`, `ls -la` | `rtk ls` |
-| `cat file` | `rtk read file` |
-| `grep pattern .` / `rg pattern` | `rtk grep pattern .` |
-| `npm test` / `cargo test` / `pytest` | `rtk test <cmd>` |
-| `npm run build` / `cargo build` | `rtk err <cmd>` |
-| `gh pr list/view` | `rtk gh pr list/view` |
-| `docker ps` | `rtk docker ps` |
-| `eslint` / `tsc` | `rtk lint` / `rtk tsc` |
-
-**Do NOT** prefix: `npx`, `npm install`, `pip install`, `node`, `python3`, heredocs, piped commands.
-
-<!-- RTK:END -->
-```
-
-### If oh-my-opencode is installed
-
-After updating AGENTS.md files, check if the omo config at `~/.config/opencode/oh-my-opencode.json` has `prompt_append` fields on agents. If it does, inform the user:
-
-> "omo is installed. For maximum coverage, you can add RTK instructions to agent `prompt_append` fields in `oh-my-opencode.json`. This ensures subagents always use rtk even when AGENTS.md is not loaded. Want me to do this?"
-
-**Only modify `oh-my-opencode.json` if the user explicitly confirms.** If they confirm, append this line to the `prompt_append` of `sisyphus-junior` agent (the primary coder):
-
-```
-\n\nRTK: ALWAYS prefix shell commands with `rtk` when available (git, ls, grep, test, build). Example: `rtk git status` not `git status`.
-```
-
-Do NOT modify other agents' prompt_append unless asked.
-
-## Phase 3: Ongoing Enforcement (EVERY time this skill is loaded)
-
-### For the current agent
-
-From this point forward in this session, **you MUST**:
-
-1. **Use `rtk` prefix** for all supported shell commands (see table above)
-2. **Verify rtk is available** before first use: `rtk --version`
-3. If rtk is not available in the current environment, fall back to normal commands silently
-
-### For subagent delegation
-
-When delegating ANY task that involves shell commands (via `task()`, `delegate_task()`, or any delegation mechanism), **ALWAYS** add this to the `MUST DO` section of the delegation prompt:
-
-```
-- Use `rtk` prefix for shell commands when available (git, ls, grep, test, build). Run `rtk --version` first to check. If not installed, use normal commands. Examples: `rtk git status`, `rtk ls`, `rtk grep pattern .`, `rtk test npm test`.
-```
-
-This is NON-NEGOTIABLE. Subagents do not read AGENTS.md, so RTK instructions MUST be passed explicitly in every delegation prompt.
-
-### Quick reference for subagent prompts
-
-Copy-paste this one-liner into MUST DO sections:
-
-> Use `rtk` prefix for all shell commands (git, ls, grep, test, build, docker). Example: `rtk git status` not `git status`. If `rtk` is not found, use normal commands.
-
-## Summary
-
-| Phase | When | What |
-|-------|------|------|
-| Detection | Always first | Check rtk installed, check omo |
-| Setup | Once (idempotent) | Append RTK block to AGENTS.md (user + project) |
-| Enforcement | Every session | Use rtk yourself, propagate to all subagents |