Home

Inspired by the Noisy Cricket — compact, composable agent primitives.

_{Works with Claude Code + Antigravity — see compatibility}

Crickets is a set of small, composable agent primitives — skills, hooks, sub-agents, MCP servers, commands, and more — grouped into native plugins for Claude Code and Antigravity. They're what you add to a project to make Agent M (agentm) effective.

📚 Get started

Install the plugins alongside Agent M and point them at your project.

• Install crickets plugins — one-liner, marketplace, or manual --plugin-dir, on Claude Code or Antigravity. (Quick version in the repo README.)

🔧 What do you want to do?

What	Plugin	Example primitives
🪶 Maintain a wiki — Diátaxis shape, your house voice, doc-watching	wiki-maintenance	style-learning loop · wiki-watcher
🔁 Run a phase-gated dev process — plan → work → review → release	developer-workflows	operator-control hooks · evaluator
🔎 Review a change adversarially — any diff or PR, no /work cycle	code-review	code review
🛡️ Guard quality + secrets — deterministic gates + a PII scan on push	cross-plugin recipe	quality gates
📋 Plan & track a project — roadmaps, plans, boards	coming soon (V5)	—

📖 Look up a detail

For devs running the plugins:

• Compatibility — which hosts and OSes are supported, and the supported_hosts contract.
• Antigravity limitations — known host gaps and the trigger that closes each.

💡 Why it works the way it does

Crickets is grounded in established practice and industry precedent — and it adapts that practice rather than following it to the letter. We take inspiration from Diátaxis for documentation (expanding from it toward a house voice, not applying it strictly), adversarial review for code, phase-gating for the dev loop, and deterministic gates ahead of LLM judgment.

• Purpose and scope — what the repo is for, and what it isn't.
• Cross-Repo Memory Protocol — how agentm and crickets share memory at phase boundaries.
• Why adversarial review — a reviewer primed to assume bugs finds real ones; a neutral "looks good" doesn't.
• Why deterministic gates run first — typecheck, lint, and tests gate before sycophantic LLM judgment.
• Why phase-gating — discrete plan → work → review → release gates beat freestyling the whole lifecycle.

🧩 Major designs

Architecture (Agent M) — the substrate crickets runs on. These are Agent M's; see its design docs rather than re-reading them here.

• Agent M memory — the MemoryVault store, the device-wide architecture, and the memory-OS unbundling. → Agent M design docs. Background: MemoryVault · memory evolution · device-wide · memory-OS.

Plugins (Crickets) — what each adds, in plain terms.

• Native host plugins (design) — author a primitive once; the generator emits native Claude Code and Antigravity plugins, installable three ways, with a CI gate that fails if dist/ drifts from src/.
• Developer plugin suite (design) — the phase-gated dev loop, the safety controls, and adversarial review, as three composable plugins joined by enhances:.
• Wiki maintenance (design) — a template-driven wiki maintainer that expands from Diátaxis toward your house voice via an operator-in-the-loop learning loop, plus the wiki-watcher.
• diataxis-author (design) — Diátaxis authoring and repair for any repo. (now an Agent M skill — see the Agent M design.)

📐 Architecture decisions

Every load-bearing call is recorded as an ADR — the "why X, and why not Y" trail, with re-audit triggers. → Browse all decisions

🤝 Want to contribute?

Building a plugin to contribute? Start with CONTRIBUTING, then the developer specs under Reference in the sidebar.