AgentSmith family API plugin — owns vault-IO, the Memory.* contract surface, the Dispatch.Agent surface, routes-cache, and the subagent-tools (ex-lifecycle) hook surface for sub-agents. Phase-2 MVP: bundled `memory.sh` and `vault-commit.sh` CLIs implementing the Memory.* contract against the AgentSmith vault (~/.secondbrain today-branch) plus a local-mode passthrough; `routes.sh` with bundled fallbacks for svc-unreachable; `dispatch.sh` as a filesystem-queue rendezvous for closed-set fix concerns; defensive + always-on subagent hooks shipped alongside the plugin. svc is a graceful fallback path, not a hard dependency. MCP server, HTTP round-trip to svc, and Haiku PII/secrets scan are deferred to Phase-2b.
Not in a marketplace yet, so it loads for one session with --plugin-dir.
Plugin agentsmith-api in SmithFamilyPlayground/agentsmith-plugins. Commands read from the repo's manifest — 1 month ago.
agentsmith-apiUse when an AgentSmith family agent needs to write to / read from the SecondBrain vault, dispatch a closed-set fix-concern subagent, look up routes, or wire in the always-on subagent-tools hooks. Implements the Memory.* contract surface, owns vault-IO via the bundled `vault-commit.sh` (today-branch
GitHub CLI runbook for AgentSmith and the SmithFamilyPlayground org — PR conventions, auto-review + daily-rollup workflow expectations, ruleset awareness, Actions triage. Bundles the `clean-gone` skill for pruning local branches whose remotes are deleted.
2 skills
Lifecycle channel for AgentSmith — push-only Claude Code channel plugin (declares claude/channel only; no tools, no permission relay). Reads NDJSON over a Unix domain socket from a local supervisor process and emits operational nudges (idle_check, context_pressure, health_pulse, external_event) as <channel source="agentsmith-comms"> notifications. Companion to the existing telegram channel — user-facing comms stay on telegram, lifecycle nudges are isolated here.
1 MCP server
Fly.io runbook for the `tod-smith` deployment — app anatomy, the always-on attachable invariant, persistence layout, Tailscale (userspace) topology, secrets rotation (incl. the VAULT_* reserved-name gotcha and Telegram bot uniqueness across fly + home box), deploy/rollback, and a triage playbook.
1 skill
sprites.dev CLI + API runbook for AgentSmith — ephemeral fly-machine workloads. Service create/update, file uploads (with the compress-over-~20MB rule), checkpoints, URL auth. Headless-Linux only; Windows/Git-Bash path-mangling material from the upstream spindev version is deliberately out of scope.
1 skill
How agents write to ~/.secondbrain: vault-commit.sh, frontmatter schema, daily-branch lifecycle, raw/ immutability.
1 skill
Continuity-of-self memory for persistent-identity Claude Code agents. Phase-1a MVP — ships a bundled `local-vault` CLI implementing the Memory.* contract (store/recall/update/list/config) against a local project vault at `<project>/.claude-persistent-memory/`, so the plugin works standalone on any project from day one (no AgentSmith / no svc / no api dependency). Phase-1b will add the dreaming-model hooks (state.md @-import + recall + consolidate-and-restart + context-pressure); phase-1c will add auto-detect-and-route to an `agentsmith-api` backend when present.
1 skill
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
AI memory system — mine projects and conversations into a searchable palace. 47 MCP tools, auto-save hooks, guided setup.
3 skills · 6 commands · 1 MCP server · hooks
Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development
9 skills · 1 command · 8 agents
Long-term semantic memory for Claude Code, powered by OpenViking
5 skills · 1 command · 1 MCP server · hooks
Persistent memory for AI coding agents -- captures tool usage, compresses via LLM, injects context into future sessions
17 skills · 1 MCP server · hooks
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.