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 skills add EZotoff/ez-omo-config --skill update-to-latestgit clone --depth 1 https://github.com/EZotoff/ez-omo-configWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ezotoff/ez-omo-config/update-to-latest)<a href="https://agentmods.dev/skills/ezotoff/ez-omo-config/update-to-latest"><img src="https://agentmods.dev/badge/skills/ezotoff/ez-omo-config/update-to-latest/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ezotoff/ez-omo-config/update-to-latest"><img src="https://agentmods.dev/badge/skills/ezotoff/ez-omo-config/update-to-latest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 155 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 385 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
What 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.1 | $0.00033 | $0.06381 |
| Opus 5 | $0.00016 | $0.03191 |
| Sonnet 5 | $0.00007 | $0.01276 |
| Haiku 4.5 | $0.00003 | $0.00638 |
Grade A, and why
update-to-latest 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 7d 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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update to Latest
Role and Purpose
This skill is a guided operational pipeline for future agents, NOT an automatic updater. It analyzes the current state, discovers available updates, produces a recommendation, and only executes after receiving explicit human approval. Future agents invoking this skill must follow every phase in order. No phase may be skipped.
Non-Goals
- This skill does NOT automatically update OpenCode or OMO.
- We do not run package manager or update commands before the approval gate.
- This skill does NOT delete patch registry entries.
- This skill does NOT claim runtime success without evidence.
13 Mandatory Workflow Phases
Phase 1: Preflight / Current-State Inventory
Before any update analysis, capture the complete current state:
- Git cleanliness in the config repo: run
git status --shortand record whether the working tree is clean. - OpenCode version: run
opencode --versionand record the output. - OMO configured source vs runtime source: discover OMO path candidates (see OMO Path Discovery below), then distinguish these evidence levels explicitly:
active_config_registered: a live OpenCode config contains afile://...oh-my-openagentorfile://...oh-my-opencodepath.live_file_installed: that path exists on disk and contains valid OMO source.runtime_loaded: a currently running OpenCode process has actually loaded that path. Do not claim this from config alone. Record the current Git branch, upstream, commit hash, package name/version, and dirty state for every valid local source candidate.
- NPM / package versions: record the installed versions of
opencode-ai,oh-my-opencode, andoh-my-openagentwhere discoverable. - Live symlink targets: verify the four symlinked configs (
opencode.json,oh-my-openagent.json,provider-connect-retry.mjs,retry-errors.json) point into this repo. - Copied plugin / skill / script inventory: list all artifacts installed by
install.shthat are NOT symlinks (e.g. plugins under~/.opencode/plugin/, scripts under~/.opencode/scripts/and~/.sisyphus/scripts/). - Active patch list: run
ls .sisyphus/patches/*.mdand record every patch entry. - Dirty state in OMO source clone: run
git status --shortin the discovered OMO directory.
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.
- 7d ago Changed · +19 lines 696b87f124bf
- 11d ago First seen · 392 lines · 33 tokens per session scan A 92af8f04755f
update-to-latest is a skill published in the GitHub repository EZotoff/ez-omo-config (6 stars, last pushed 6d ago), licensed MIT. It adds 33 tokens to every session and 6,381 once invoked, about $0.0002 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
omc-plan
Strategic planning with optional interview workflow.
ralph
Self-referential loop until task completion with configurable verification reviewer.
self-improve
Autonomous evolutionary code improvement engine with tournament selection.
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…
launch
Shipyard's governed delivery pipeline — converge the mission, synthesize a durable spec, decompose vertical-slice tickets with blocking edges, run the frontier in parallel via team, close with verification, and report with a full decision log. Two entry gates — the yard gate (drydock audit) and the fog gate (an effort…
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.