Most agent projects do not fail because the first model call is difficult. They become difficult when the prototype needs memory, tools, evaluation, a user interface, documentation that coding agents can navigate, and a repeatable review process.
That is the problem the open-source AgentsKit ecosystem is trying to solve for JavaScript teams. It is a set of independent projects with shared contracts, rather than one application that must own the whole stack.
The six public pieces
1. AgentsKit: the composable foundation
defines an interactive agent experience once and renders it through React, React Native, Ink, Vue, Svelte, Solid, or Angular.
It also supports deterministic local answers before an optional backend call. That matters for documentation and support interfaces where exact project facts should not require an LLM.
3. Registry: reusable source, not another dependency
The turns engineering practices for coding agents into inspectable patterns, prompts, templates, and zero-dependency gates.
Instead of telling an agent to “write production-quality code,” a team can define package boundaries, required evidence, review rules, and executable checks. The repository currently verifies 87 production patterns, six engineering pillars, six SDLC phases, and 13 gate scripts from its own source.
5. Doc Bridge: tell agents where they may work
runs locally or as a GitHub Action. It supports existing Codex and Claude CLI logins, hosted providers, gateways, and local Ollama models.
Seven review lenses generate candidate findings. Independent verification votes then remove weak findings before the result reaches the developer.
npx --yes github:AgentsKit-io/code-review-cli --provider codex-cli
The output can be Markdown, GitHub review comments, or SARIF.
How the pieces fit
You do not need to adopt everything:
- Use AgentsKit when you need composable runtime capabilities.
- Add Chat when the same agent experience must run across web, native, and terminal interfaces.
- Copy from the Registry when a ready agent is a better starting point than a blank file.
- Use the Playbook to establish contribution and quality rules.
- Add Doc Bridge when agents need deterministic ownership, documentation, and validation routes.
- Run Code Review when agent-authored changes need a low-noise verification layer.
Each repository is independently usable and openly licensed. The shared objective is interoperability: a team should be able to start with one package and add another without replacing its existing architecture.
Where contributions help most
The ecosystem is looking for more than implementation code. Useful contributions include provider adapters, framework examples, reusable agents, false-positive reductions, documentation adapters, executable gates, fixtures, and clearer onboarding.
If one of these problems matches work you are already doing, try the smallest relevant project, report what did not compose cleanly, and consider starring the repositories you want other JavaScript developers to discover.
SOCIAL SHARE CARD GENERATOR