by waybarrios
Eleven Claude Code skills ported to OpenCode: code-review, security-review, feature-dev, frontend-design + 7 more. One config line, one plugin.
# Add to your Claude Code skills
git clone https://github.com/waybarrios/opencode-power-packGuides for using ai agents skills like opencode-power-pack.
Last scanned: 5/27/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-05-27T08:04:10.623Z",
"semgrepRan": false,
"npmAuditRan": true,
"pipAuditRan": true
}opencode-power-pack is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by waybarrios. Eleven Claude Code skills ported to OpenCode: code-review, security-review, feature-dev, frontend-design + 7 more. One config line, one plugin. It has 386 GitHub stars.
Yes. opencode-power-pack passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/waybarrios/opencode-power-pack" and add it to your Claude Code skills directory (see the Installation section above).
opencode-power-pack is primarily written in JavaScript. It is open-source under waybarrios on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh opencode-power-pack against similar tools.
No comments yet. Be the first to share your thoughts!
OpenCode reads Claude Code's SKILL.md format natively, but most of Anthropic's official Claude Code plugins put their value in commands/ and agents/ — and those are Claude-Code-only. So if you want /code-review, /security-review, or /feature-dev in OpenCode, copy-paste won't get you there.
This pack does the translation: the multi-agent workflows from those plugins are rewritten as OpenCode-compatible skills, so the methodology survives the platform jump. Plus a few direct ports of skills that already lived in Anthropic's skills/ repo.
It pairs nicely with obra/superpowers, which provides the meta-workflow skills (brainstorming, TDD, executing-plans). This pack adds the domain-specific muscle.
npm install step at startup is automaticTwo paths that work today; pick whichever fits how you plan to use the pack.
| A — Install from GitHub | B — Install from a local git clone | |
|---|---|---|
| Best for | Just using the pack | Tinkering, contributing, or running offline |
| Requires | Network during first install | A local clone of the repo |
| Updates | git pull + cache clear (the cache holds Bun's checkout) |
git pull updates everything live; symlinks pick up changes immediately |
| Internet at runtime | Only at first install / on cache miss | Never |
Both methods share steps 2 (symlink commands) and 3 (restart). Only step 1 differs.
Step 1A. Add to ~/.config/opencode/opencode.json:
{
"$schema": "https://opencode.ai/config.json",
"plugin": [
"opencode-power-pack@git+https://github.com/waybarrios/opencode-power-pack.git"
]
}
If you already use other plugins (e.g. superpowers), keep all of them in the array:
{
"plugin": [
"superpowers@git+https://github.com/obra/superpowers.git",
"opencode-power-pack@git+https://github.com/waybarrios/opencode-power-pack.git"
]
}
To pin a specific tag (recommended once releases exist):
"opencode-power-pack@git+https://github.com/waybarrios/opencode-power-pack.git#v0.2.0"
You still need a local copy of the repo for step 2 (the slash command files live there). Clone it next to wherever you keep code:
git clone https://github.com/waybarrios/opencode-power-pack.git ~/code/opencode-power-pack
Then jump to step 2 (symlink commands) below.
This avoids the GitHub round-trip entirely. The plugin lives on your disk, and OpenCode reads it via a file:// URL.
Step 1B.1. Clone the repo wherever you keep code:
git clone https://github.com/waybarrios/opencode-power-pack.git ~/code/opencode-power-pack
If the repo is not yet on GitHub and you only have it locally, skip the clone — just point at the existing directory.
Step 1B.2. Add to ~/.config/opencode/opencode.json, using the absolute path to your clone:
{
"$schema": "https://opencode.ai/config.json",
"plugin": [
"opencode-power-pack@git+file:///Users/you/code/opencode-power-pack"
]
}
Notes:
file:// URL needs to be an absolute path with three slashes (file:///Users/...) and no trailing slash..git/). If you copied the files without git, run git init && git add . && git commit -m init inside the directory first — Bun's git-style installer requires a real git tree.cd ~/code/opencode-power-pack && git pull, then clear the cache and restart (see Updating).Then continue to step 2 below.
The plugin auto-registers the skills directory programmatically. Slash commands, however, need to live in OpenCode's canonical commands path; the plugin ships physical markdown files under commands/ for you to symlink in.
mkdir -p ~/.config/opencode/commands
ln -s ~/code/opencode-power-pack/commands/*.md ~/.config/opencode/commands/
Adjust the source path if you cloned somewhere other than ~/code/opencode-power-pack. If a command of the same name already exists in ~/.config/opencode/commands/, that file wins — ln -s will refuse to overwrite, which is the desired behavior.
If you prefer copies over symlinks (e.g. you do not want git pull to silently change your commands):
cp ~/code/opencode-power-pack/commands/*.md ~/.config/opencode/commands/
Trade-off: copies are static — you have to re-copy after every git pull. Symlinks track the working tree live.
# kill ALL opencode processes (not just the active TUI)
pkill -f opencode
# clear the npm-style plugin cache so the new version is fetched fresh
rm -rf ~/.cache/opencode/node_modules/opencode-power-pack 2>/dev/null
# start again
opencode
In a new OpenCode session, run:
List the skills you have available.
You should see the eleven skills under the opencode-power-pack: namespace (or unprefixed, depending on your OpenCode version).
Then hit ctrl+p to open the command palette and look for any of:
code-reviewsecurity-reviewfeature-dev