npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@jabworks/condux

v0.28.0

Published

OpenCode plugin for the condux workflow toolkit — bundles the condux skills and injects the specialist agents (coder, explorer, planner, researcher) plus an opt-in plan-review listener.

Readme

@jabworks/condux

OpenCode plugin for the condux workflow toolkit. One plugin line installs everything condux needs:

  • Skills — bundles the 14 condux workflow skills (workflow, discovery, draft-plan, test-first-development, subagent-execution, subagent-deployment, finalize, live-verification, code-review, preflight, root-cause-analysis, plan-review, technical-spec, condux-doctor) and registers them on config.skills.paths via the config hook — no separate npx skills add step. A skill you install yourself under the same name still wins; OpenCode dedupes by name.
  • Agents — injects the four condux specialist agents (coder, explorer, planner, researcher) as subagents via the same hook, carrying the tool restrictions their canonical definitions declare: explorer and researcher are read-only (no edit, write, or bash) and planner cannot run shell commands. If your opencode.json already defines an agent with the same name, yours wins — injection is skip-if-present.
  • Plan-review listener (opt-in) — with CONDUX_PLAN_REVIEW=1, when the primary plan agent finishes a turn, spawns the plan-review annotate server (from the bundled skills, or any discoverable skill tree). Best-effort: OpenCode does not await event hooks, so this cannot block the next turn on the review outcome (unlike the Codex Stop hook).

Install

Add @jabworks/condux to your opencode.json and restart OpenCode:

// opencode.json
{
  "plugin": ["@jabworks/condux"]
}

That's the whole install — skills and agents come with the plugin. The other agentic-toolkit skills (git-commit, session-handoff, release, spec-browser, …) are not part of condux; install those separately if you want them:

npx skills add https://github.com/jabworks/agentic-toolkit/tree/main/dist/opencode/skills -a opencode

Notes

  • Injected agents carry no model pin — they inherit your session default. To restore the toolkit's tiering (e.g. a cheap model for explorer), override in opencode.json: "agent": { "explorer": { "model": "anthropic/<model-id>" } }.
  • Restrictions are expressed as OpenCode permission denials, not the deprecated tools map — tools is folded into permissions while the config file is parsed, which is over before a plugin's config hook runs, so a tools map injected there has no effect. Only the bash and edit gates cross over (edit covers edit/write/patch). Read-side tools keep OpenCode's defaults, because the Claude allowlists omit Grep/Glob while the prompts still expect to search — denying those would break the agents rather than constrain them.
  • The plan-review listener finds plan-review/references/annotate-server.js in the bundled skills first, then any discoverable skill tree (.opencode/skills/, .agents/skills/, .claude/skills/, or their global equivalents).
  • OpenCode caches npm plugins under ~/.cache/opencode/. If an upgrade seems to have no effect, clear that cache and restart OpenCode.
  • The agents/ and skills/ trees are generated from the toolkit's canonical sources by scripts/build-opencode.mjs — edit the sources in the toolkit repo (skills/subagent-execution/agents/ and skills/<name>/), not here.