Install Crickets Plugins

How to install crickets plugins

Note

Goal: Install the crickets plugins into Claude Code and/or Antigravity as native host plugins. Prereqs: claude (Claude Code) and/or agy (Antigravity) on your PATH; git. No clone needed for the one-liner or the Claude marketplace.

crickets ships as native host plugins generated from one source; the old install.sh dispatcher is gone (Build system design). The default set is thirteen (the full roster); these six are the ones the examples below use:

Plugin	Standalone?	What it adds
development-lifecycle	yes (base)	the six phase commands (/setup /plan /work /review /release /bugfix) + the explorer/evaluator agents + the harness-context SessionStart hook (Claude-only).
developer-safety	enhances development-lifecycle	the kill-switch / steer / commit-on-stop hooks + the commit-no-coauthor / worktrees-operator-initiated conventions.
code-review	enhances development-lifecycle's review	the adversarial-reviewer + cross-model adversarial-reviewer-cross agents, the evidence-tracker hook, and the standalone /code-review command.
maintenance	requires development-lifecycle	CI workflows + dependabot-fixer.
privacy	standalone	the PII guardrail — scrubber skill + pre-push detector.
wiki	enhances development-lifecycle's documentation	Diátaxis wiki authoring + maintenance.

There are three ways to install — the one-liner, per-plugin by name or path, or a single plugin with no marketplace — and every route lands the same plugins, so pick whichever fits how much setup you want.

Steps

Option 1 — the one-liner (recommended). Installs the default set on whichever host(s) are present:

curl -fsSL https://raw.githubusercontent.com/alexherrero/crickets/main/bootstrap.sh | bash

It detects claude / agy: on Claude Code it adds the crickets marketplace and installs by name; on Antigravity it installs each plugin by path (the asymmetry below).

Option 2 — by name (Claude) or by path (Antigravity).

Important

The name@crickets marketplace syntax is Claude-only. Antigravity's agy has no marketplace-registration command, so install each plugin by its dist/antigravity/plugins/<group> path instead.

Claude Code — add the marketplace once, then install each plugin you want by name, one command per plugin (the names below are examples — install only what you need):

claude plugin marketplace add alexherrero/crickets
claude plugin install development-lifecycle@crickets
claude plugin install code-review@crickets
# repeat for any of: developer-safety, maintenance, privacy, wiki

Antigravity (agy 1.0.2 or later) — by path from a clone. agy resolves no cross-plugin dependencies, so install development-lifecycle first: six plugins require it (conventions, design, diagnostics, github-projects, maintenance, research), and installing one of them alone leaves its requires: unsatisfied.

git clone https://github.com/alexherrero/crickets.git ~/Antigravity/crickets
for p in development-lifecycle developer-safety code-review maintenance privacy wiki; do
  agy plugin install ~/Antigravity/crickets/dist/antigravity/plugins/$p
done

To let the order be worked out for you, ask the resolver the one-liner uses — it topologically sorts any set of plugins over their declared requires: and fails loudly on a cycle:

python3 ~/Antigravity/crickets/scripts/resolve_install_order.py ~/Antigravity/crickets/dist/claude-code/.claude-plugin/marketplace.json development-lifecycle maintenance wiki

Option 3 — one plugin, no marketplace. Good for trying a single plugin. On Claude Code, load it for one session:

claude --plugin-dir ~/Antigravity/crickets/dist/claude-code/plugins/privacy

On Antigravity, the same agy plugin install <path>, pointed at any one dist/antigravity/plugins/<group> dir.

Verify

claude plugin list      # the @crickets plugins, enabled (user scope)
agy plugin list         # the imported plugins

Some plugins have limited compatibility on Antigravity — see Compatibility for the per-plugin details.

See also

• Using code review — a hands-on first run of one plugin.
• Modify a crickets plugin — the source → generate → dogfood loop.
• Compatibility — the per-host component + hook matrix.