cyberlife-coder/VelesDB

The explainable, local-first memory engine for AI agents. One ~9 MB binary fuses vector + graph + columnar under VelesQL; why() returns the evidence path behind every recall. No cloud, no glue code — runs on server, browser, mobile and desktop.

90Stars on the repository
7Mods indexed here, across every type
2d agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied

core-parity-audit

01

cyberlife-coder/VelesDB

Skill Claude CodeCodex

Re-run the VelesDB core-vs-ecosystem gap analysis (code + documentation). Use when asked to audit API parity, check that every crate/SDK/integration/doc has caught up to velesdb-core, verify the core↔children architecture is clean, or produce a parity matrix. velesdb-core is the single source of truth; the VelesDB…

90 2d ago A 91 tokens

velesdb-memory

02

cyberlife-coder/VelesDB

Skill Claude CodeCodex

Use durable, explainable, self-improving memory across a coding session via the velesdb-memory MCP server. Trigger whenever the velesdb-memory MCP tools (remember/recall/recallfused/relate/why/feedback/forget/rememberextracted/extractionstatus/entity/memorystatus) are available and the work would benefit from…

90 2d ago A 328 tokens

cyberlife-coder/VelesDB

Skill Claude CodeCodex

Compress an agent's working context deterministically with VelesDB's context compiler before sending it to a model — fewer tokens, same facts, every decision auditable and reversible. Use when a prompt is bloated with repeated context, long logs, or accumulated conversation turns; when token costs need to drop…

90 2d ago A 175 tokens

cyberlife-coder/VelesDB

Skill Claude CodeCodex

Turn every velesdb design / implement / verify cycle into durable, connected memory so the SAME mistake is never repeated and later decisions build on what was already learned, instead of re-deriving it or silently colliding with it. Trigger BEFORE starting a design or implementation on velesdb / velesdb-core /…

90 2d ago A 275 tokens