Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/ezotoff/ez-omo-config/patch-opencodenpx skills add EZotoff/ez-omo-config --skill patch-opencodegit clone --depth 1 https://github.com/EZotoff/ez-omo-configWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00053 | $0.02334 |
| Opus 5 | $0.00026 | $0.01167 |
| Sonnet 5 | $0.00011 | $0.00467 |
| Haiku 4.5 | $0.00005 | $0.00233 |
Grade A, and why
patch-opencode scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Patch OpenCode Binary
This skill applies a minimal source fix to the live OpenCode binary. It builds from the exact release tag that matches the running version — never from dev or any other branch.
Pre-flight Checks
Before starting, gather the facts:
# 1. Identify the live version
LIVE_VERSION=$(~/.opencode/bin/opencode --version 2>&1)
echo "Live version: $LIVE_VERSION"
# 2. Identify the source repo
SOURCE_DIR="${OPENCODE_SOURCE:-$HOME/src/opencode}"
cd "$SOURCE_DIR"
# 3. Verify the release tag exists
git tag --list "v${LIVE_VERSION}"
# Expected: v1.17.9 (or whatever the live version is)
# If empty, the version tag doesn't exist — do NOT proceed with dev branch
# 4. Check for running servers
ps -ef | grep 'opencode serve' | grep -v grep
Critical Rules
- NEVER build from
origin/devor any branch other than the release tag - NEVER replace the live binary with a build that reports a different version
- ALWAYS backup the live binary before replacing
- ALWAYS build with
--single --skip-install --skip-embed-web-uifor speed - ALWAYS verify the build version matches the live version before installing
- ALWAYS test the fix on the real surface after installing
Procedure
Step 1: Check out the release source
SOURCE_DIR="${OPENCODE_SOURCE:-$HOME/src/opencode}"
cd "$SOURCE_DIR"
LIVE_VERSION=$(~/.opencode/bin/opencode --version 2>&1)
# Fetch latest tags
git fetch --tags origin
# Verify the source tree is clean before checkout
if [ -n "$(git status --porcelain)" ]; then
echo "FATAL: Source tree is dirty. Commit or stash before checking out the release tag."
git status --porcelain
exit 1
fi
# Create a fix branch from the EXACT release tag
git checkout "v${LIVE_VERSION}" -b "fix/${FIX_NAME}"
Guard: If v${LIVE_VERSION} tag doesn't exist, STOP. Do not proceed with any other branch. The version tag is the contract.
Warning: Tags like v0.1.17* are NOT the same as v1.17*. Verify the tag matches the live version output.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 231 lines · 53 tokens per session scan A 70644f2f513a
patch-opencode is a skill published in the GitHub repository EZotoff/ez-omo-config (5 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 2,334 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
fusion-setup
Use when a user wants to set up, configure, install, or reconfigure the opencode Fusion agent team - a strong main/build agent that plans and reviews but cannot edit files, delegating all edits to a cheaper sidekick subagent, plus an explore search agent and optional research/design/reviewer/vision specialists.…
configure-notifications
Configure notification integrations (Telegram, Discord, Slack) via natural language.
autopilot
Full autonomous execution from idea to working code.
drydock
Lay the keel of the shipyard harness in any repo — the 4-pillar shared environment (Context, Rules, Tools, Standards) across 5 surfaces (CLAUDE.md, skills, design-system, mcp/cli, shared context) so that every human and agent inherits the same design language and anyone can ship. Run once per repo; re-run with --check…
deepinit
Deep codebase initialization with hierarchical AGENTS.md documentation.
graph
Deterministic orchestration graph runtime - declarative DAG pipelines with journal-based crash recovery.