Home

Inspired by the Noisy Cricket — agent primitives that punch far above their weight.

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

Crickets is the noisy cricket — small, focused agent customizations that punch above their weight. Skills, hooks, sub-agents, bundles, MCP servers, slash commands, status lines, output styles, workflows, rules, snippets, settings-fragments. The primitives you carry into any project to make Agent M (agentm) effective.

This wiki is the contributor-facing documentation for Crickets itself. Every page is written for a single reader intent (learn / do / look up / understand) per the Diátaxis convention.

Note

Repo: github.com/alexherrero/crickets. Public, MIT-licensed. PII guardrails (script + skill + pre-push hook) are foundational — see Purpose and scope for why.

📚 New here? Learn by doing.

• Tutorial 1 — Your first customization — add a hello-world skill, install it into a scratch project, see it land at three host paths. ~10 minutes.

🔧 Trying to do something specific?

• Install crickets plugins — three install modes (one-liner / marketplace / manual) across Claude Code + Antigravity.
• Develop a crickets plugin locally — the source → generate → dogfood → commit loop.
• Add a skill — add a new standalone skill.
• Quality-Gates-Recipe — operator-facing recipe for the 5-primitive quality-gates set (replaces the v1.x quality-gates bundle; kind: bundle reserved-future in v2.0.0).
• Use the evaluator — dispatch the evaluator sub-agent for PASS / NEEDS_WORK grading against a precise rubric.
• Use the base hooks — kill-switch, steer, commit-on-stop. Operator-precision control for long-running Claude Code sessions.

The evidence-tracker hook and the design, memory, and diataxis-author skills, along with Antigravity plugin authoring, moved to Agent M in v2.0.0 (V4 #36 reorg). See the Agent M wiki for their operational docs.

📖 Looking up a detail?

• Customization Types — what each of the 13 kinds means and where to put them (kind: bundle + kind: plugin reserved-future in v2.0.0).
• Manifest Schema — YAML frontmatter contract.
• Per-Host Paths — destination paths per kind per host.
• Installer CLI — flags, prereqs, exit codes.
• Compatibility — supported hosts (Claude Code, Antigravity) + OS matrix + per-manifest supported_hosts contract.

💡 Want to know why?

• Purpose and scope — what this repo is for, what it's not.
• Cross-Repo Memory Protocol — how agentm reads from + writes to the toolkit-side /memory skill at phase boundaries.
• V3 Retrospective — what shipped, what we learned, what's next (closes the V3 arc; ships with harness v3.0.0 + toolkit v1.0.0).
• Agent Memory Evolution: From ContextVault to V7 — V1→V7 HLD of the AgentMemory architecture (V3 ships with this release; V4+ is roadmap-deferred).
• Device-Wide Architecture — V4 architectural shift from per-repo harness to device-wide agentic OS; rationale for the agentm/crickets split + which primitives live where.
• Memory-OS Architecture — V5, the unbundling: agentm becomes a storage-agnostic memory OS + plugin host; the workflow/docs/PM/storage capabilities unbundle into crickets plugins. The memory↔process + memory↔storage seams, the device-local default, and the vault-conserving cutover.

Architecture decisions

• ADR 0001 — crickets purpose, scope, public-with-PII-guardrails
• ADR 0002 — evaluator sub-agent design
• ADR 0003 — base operator-control hooks
• ADR 0004 — design skill: human-facing design pipeline → agent execution handoff
• ADR 0006 — Gemini CLI host removal
• ADR 0007 — MemoryVault Discovery + Mining
• ADR 0008 — diataxis-author skill
• ADR 0009 — evidence-tracker hook
• ADR 0011 — Antigravity 2.0 host support
• ADR 0012 — device-wide-by-default
• ADR 0013 — bundles are native host plugins
• ADR 0014 — #40 install-decoupling
• ADR 0015 — #36 partial-revision
• ADR 0016 — Project surface split

Designs

The canonical "Why we built X" entry points (published via the /design skill, surfaced here when the parent design's last queued part hits Status: done and harness /release transitions the design to launched).

• MemoryVault — permanent agent memory via Obsidian-vault-folder + reflection sidecar — single memory skill in crickets with sub-commands save / evolve / reflect / search; SessionStart + UserPromptSubmit recall hooks; reflection sidecar with tri-modal confidence routing; two-tier idea capture (Ideas.md surface + _idea-incubator/ deep research); planned in 6 parts across plans #7a (5 parts) + #7b (1 part). See parts: write-primitives, recall-loop, reflection-and-recovery, idea-ledger, seed-pass, discovery-mining.
• diataxis-author — Diátaxis wiki authoring + maintenance for any repo — second major skill after memory; subsumes the harness's migrate-to-diataxis predecessor; AgentMemory-integrated conventions; planned in 5 parts. See parts: skill-scaffold, author-classify, check-repair, migrate-subsume, agentmemory-docs-release.
• Crickets v3.0 — Native Host Plugins from a Single Source of Truth — retires the bespoke install.sh dispatch for a single source of truth + a generator emitting native Claude Code + Antigravity plugins (folder-per-group; committed dist/ + a generated-in-sync CI gate; native dependencies on Claude, thin-separate on Antigravity); three install modes (one-line default installer / marketplace / manual pick-and-choose); decouples the agentm↔crickets lib/install/ byte-sync. Status: final, planned in 6 parts. See parts: foundations, generator-claude, antigravity-emitter, ci-gate, distribution-clean-break, dogfood-proof-docs.

Conventions

Page templates, filename rules, and the Diátaxis four-mode split mirror the sibling repo's documentation convention — see agentm/harness/documentation.md. The mode-purity lint (scripts/check-wiki.py --strict) is the same.