opencode-nj-kit
v0.1.0
Published
Drop-in skills, subagents, slash commands, and global AGENTS.md for OpenCode. 20 specialist agents, 37 skills, 10 slash commands.
Downloads
60
Maintainers
Readme
opencode-nj-kit
A drop-in kit for OpenCode that installs:
- AGENTS.md — global routing/enforcement instructions that make skills and subagents actually fire
- 20 specialist subagents — frontend, backend, mobile, database, devops, security, debugger, orchestrator, and more
- 37 skills — clean-code, systematic-debugging, tailwind, React/Next.js, API, DB, perf, sec, SEO, GEO, and more
- 10 slash commands —
/plan,/debug,/test,/orchestrate,/deploy, etc.
Install
# One-shot, recommended
bunx opencode-nj-kit
# or
npx opencode-nj-kitThat's it. The CLI:
- Detects your OpenCode config dir (
$XDG_CONFIG_HOME/opencodeor~/.config/opencode) - Asks what to install (defaults: everything)
- Asks how to handle existing files (default: backup to
.bakthen overwrite) - Adds
"instructions": ["./AGENTS.md"]to youropencode.jsonif missing - Done — open OpenCode and run
/agentsto see the new specialists
Commands
opencode-nj-kit # init (interactive)
opencode-nj-kit init --yes # non-interactive, backup mode
opencode-nj-kit list # show what's bundled
opencode-nj-kit update # re-copy from template
opencode-nj-kit uninstall # remove kit files (.bak kept)Flags
| Flag | Effect |
|---|---|
| --yes, -y | Non-interactive, accept defaults |
| --force | Overwrite without backup |
| --skip-existing | Never touch existing files |
| --backup | Backup .bak before overwriting |
| --dry-run | Show plan, write nothing |
What gets installed where
~/.config/opencode/
├── AGENTS.md ← global instructions
├── agents/ ← 20 *.md agents (mode: all)
├── skills/<name>/SKILL.md ← 37 skills
└── commands/ ← 10 slash commandsopencode.json is patched in-place to ensure instructions: ["./AGENTS.md"]
is set. If you don't have an opencode.json yet, the patch step is skipped
silently.
Why a CLI installer instead of an OpenCode plugin?
OpenCode's plugin API (@opencode-ai/plugin) hooks runtime events — it
doesn't ship skills/agents/commands. So the right shape for content packs is a
shadcn-style copy-into-config installer: it gives users full ownership of the
files, lets them customize, and keeps updates explicit.
Updating
bunx opencode-nj-kit@latest updateExisting files are backed up to *.bak before overwrite by default, so you
can diff and merge your local changes back in.
Uninstall
bunx opencode-nj-kit uninstallRemoves everything the kit copied. Your .bak files stay so you can restore.
License
MIT
