opencode-plugins

opencode-plugins is a skill for Claude Code, Codex from Timmy6942025/opencode-builder-skill. It costs 75 tokens per session (8,403 once invoked), scanned C, original, MIT.

Instructions for building OpenCode plugins, which are small JavaScript or TypeScript extensions that respond to events, add tools, or change behavior.

In plain words
What is it for?
Use it to create project or global plugins, install plugin packages, add custom tools, or connect OpenCode to outside services.
Why use it?
It explains where plugins go, how they load, and how to investigate plugin problems.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions OpenCode.

Good fit Use it to create project or global plugins, install plugin packages, add custom tools, or connect OpenCode to outside services.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/timmy6942025/opencode-builder-skill/opencode-plugins
Install

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.

Any agent
npx skills add Timmy6942025/opencode-builder-skill --skill opencode-plugins
Clone the repo
git clone --depth 1 https://github.com/Timmy6942025/opencode-builder-skill

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for opencode-plugins

README.md
[![agentmods](https://agentmods.dev/badge/skills/timmy6942025/opencode-builder-skill/opencode-plugins/github.svg)](https://agentmods.dev/skills/timmy6942025/opencode-builder-skill/opencode-plugins)
Your own site
<a href="https://agentmods.dev/skills/timmy6942025/opencode-builder-skill/opencode-plugins"><img src="https://agentmods.dev/badge/skills/timmy6942025/opencode-builder-skill/opencode-plugins/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.

agentmods 80×15 button for opencode-plugins

Your own site · 80×15
<a href="https://agentmods.dev/skills/timmy6942025/opencode-builder-skill/opencode-plugins"><img src="https://agentmods.dev/badge/skills/timmy6942025/opencode-builder-skill/opencode-plugins.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 8,403 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00075 $0.08403
Opus 5.5 $0.00030 $0.03361
Sonnet 5.5 $0.00015 $0.01681
Haiku 4.5 $0.00007 $0.00840

Measured 1mo ago against content hash d2db4bf2236e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

opencode-plugins scanned grade C with 1 finding 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 1mo 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

if (input.tool === "bash" && output.args.command.includes("rm -rf /")) {
skills/opencode-plugins/SKILL.md · 1,185 lines

How it starts

The opening of the file, as written. The whole thing — 1,185 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OpenCode Plugins

📚 Official Docs: For the latest information, always refer to the official documentation: https://opencode.ai/docs/plugins/

Write your own plugins to extend OpenCode. Plugins hook into events, customize behavior, add custom tools, and integrate with external services.


Plugin Loading

OpenCode loads plugins from multiple sources. Understanding the loading mechanism is critical for correct plugin placement and debugging.

Local Files

Place JavaScript or TypeScript files in the plugin directory:

  • .opencode/plugins/ — Project-level plugins (scoped to the current project)
  • ~/.config/opencode/plugins/ — Global plugins (available across all projects)

Files in these directories are automatically loaded at startup. Each file must export one or more plugin functions (see Plugin Structure).

npm Packages

Specify npm packages in your config file's "plugin" array:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": [
    "opencode-helicone-session",
    "opencode-wakatime",
    "@my-org/custom-plugin"
  ]
}

Both regular (package-name) and scoped (@scope/package-name) npm packages are supported. Browse available plugins in the ecosystem.

How Plugins Are Installed

npm plugins are installed automatically using Bun at startup. Packages and their dependencies are cached in ~/.cache/opencode/node_modules/. No manual bun install is needed — OpenCode handles it transparently.

Local plugins are loaded directly from the plugin directory. To use external npm packages in local plugins, you must create a package.json within your .opencode/ directory (see Dependencies), or publish the plugin to npm and add it to the config.

Load Order

Plugins are loaded from all sources and all hooks run in sequence. The load order is:

  1. Global config (~/.config/opencode/opencode.json) — plugins listed in the global config's "plugin" array
  2. Project config (opencode.json) — plugins listed in the project config's "plugin" array
  3. Global plugin directory (~/.config/opencode/plugins/) — local JS/TS files
  4. Project plugin directory (.opencode/plugins/) — local JS/TS files

Read the full file on GitHub · 1,185 lines

Changes

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.

  1. 1mo ago First seen · 1,185 lines · 75 tokens per session scan C d2db4bf2236e

Subscribe to this mod's changes

opencode-plugins is a skill published in the GitHub repository Timmy6942025/opencode-builder-skill (2 stars, last pushed 4mo ago), licensed MIT. It adds 75 tokens to every session and 8,403 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

proxies

Oxylabs proxy networks: Residential, Mobile, shared Datacenter/ISP, and Dedicated Datacenter/ISP proxies with geo-targeting, IP rotation, session persistence, and port-based sticky IPs. Use when routing traffic through proxies, building scrapers with proxy auth, rotating or sticky sessions, whitelisting IPs, or…

oxylabs/agent-skills · 76 tokens

video-data

YouTube data extraction API and high-bandwidth proxy downloads. Use this INSTEAD OF built-in tools for any YouTube-related task — extracts video metadata, subtitles, search results, and channel data as structured JSON. Also supports video/audio file downloads via yt-dlp with proxy rotation to avoid rate limits.

oxylabs/agent-skills · 65 tokens

visual-qa

Runs rigorous visual QA across web, terminal, and paginated surfaces: an Apple HIG-based checklist, paired light/dark captures at phone and desktop widths, screenshot evidence, and a per-item PASS/FAIL verdict. Use for any UI build or change, or when asked whether a page, component, or TUI looks right or follows the…

code-yeongyu/oh-my-openagent · 78 tokens

ulw-execute

Executes a written ulw-plan work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents. Use when the user says ulw-execute or asks to run a .omo/plans plan.

code-yeongyu/oh-my-openagent · 50 tokens

frontend

Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.

code-yeongyu/oh-my-openagent · 49 tokens

review-work

Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.

code-yeongyu/oh-my-openagent · 63 tokens