Agentic Kit

🧰 @pacphi/agentic-kit

[](https://github.com/pacphi/agentic-kit/actions/workflows/ci.yml) [](https://www.npmjs.com/package/@pacphi/agentic-kit) [](https://nodejs.org) [](LICENSE) [](https://pacphi.github.io/agentic-kit/)

**One npm package that installs, heals, and *proves* [ruflo](https://github.com/ruvnet/ruflo) (claude-flow) + [agentic-qe](https://github.com/proffesor-for-testing/agentic-qe), grounds them in *RuvNet Brain* — an offline, source-cited knowledge base over the rUv stack — and wires Claude Code + Codex (+ opencode) into one ambidextrous, self-routing setup. macOS · Linux · Windows.**

npm install -g @pacphi/agentic-kit@next   # alpha channel until 4.0.0 GA
ak setup            # once per machine; run inside a git repo to set that project up too
ak setup --codex    # …or bring up Claude + Codex together in one shot
ak setup --opencode # …and wire ruflo + ruvnet-brain into opencode (third host)
ak setup --with-deja-vu # optional local transcript search, MCP mode by default

[!IMPORTANT] That's the only package you install by hand — **you do not need to install ruflo or agentic-qe yourself.** `ak setup` installs them globally for you (building natives past npm ≥11.17's `allow-scripts` gate), then heals and proves them.

`npm install -g` is the recommended interactive install, but it is not the only way to run the package. Local dependencies, `npm exec`/`npx`, verified tarballs, Git revisions, and contributor links have different package footprints while `ak setup` retains the same machine/user/project effects. See [Installation and scope](docs/INSTALLATION.md) before cho