cogni

Stores and retrieves synthetic semantic memory signatures in a local SQLite database for AI agents.

1|Updated Jul 18, 2025
One-click install
npx skills add https://github.com/AdelysAlberto/md-configs-and-agents --skill cogni-adelysalberto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cogni
Source: https://github.com/AdelysAlberto/md-configs-and-agents/tree/main/agents-copilot/skills/cogni
Command: npx skills add https://github.com/AdelysAlberto/md-configs-and-agents --skill cogni-adelysalberto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents repeatedly re-read source code and documentation across chat sessions, inflating token consumption and losing architectural decisions after context compaction. Cogni persists compact semantic memory signatures in a local SQLite database so agents can recall prior decisions, bugfixes, and patterns without re-analyzing the codebase. ## Core Features & Use Cases - Two-Step Retrieval: Run a lightweight cogni search to find relevant memory IDs, then hydrate full content only for matching entries with cogni get, keeping context usage minimal. - High-Density Signatures: Save structured memories with What/Why/Where/Learned fields, deterministic topic keys, and automatic upserts to prevent duplicates. - Session Lifecycle Management: Persist end-of-session summaries and instantly restore context after compaction using cogni_session_summary and cogni_context. - Use Case: Before fixing a JWT authentication bug, an agent searches Cogni for prior resolutions in the auth module, retrieves the exact signature describing the previous fix, and applies the established pattern without re-reading hundreds of lines of code. ## Quick Start Ask your AI agent to search Cogni memory for previous decisions about the module you are working on before starting the task.

Frequently Asked Questions about cogni

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I give an AI agent persistent memory across sessions?▼

Use Cogni to save structured memory signatures into a local SQLite database with the cogni save command or MCP tool. At the start of each session, call cogni_context to reload recent decisions, conventions, and session summaries in under 100 tokens.

How do I reduce token usage when an AI agent reads my codebase?▼

Replace repeated file reads with high-density synthetic signatures stored via Cogni. Agents run a lightweight cogni search first, then hydrate full content only for matching IDs, cutting input token consumption by up to 95 percent.

Does Cogni work with Cursor, Claude, and GitHub Copilot?▼

Yes, Cogni is designed for AI agent environments including Antigravity, Cursor, Claude, Copilot, OpenCode, Hermes, and Codex. It exposes both CLI commands and native MCP tools that these agents can invoke.

What should an AI agent save to memory and what should it skip?▼

Save high-signal entries such as non-trivial bugfixes, architectural decisions, discoveries, configs, patterns, and session summaries. Skip trivial metadata changes, typo fixes, formatting, and anything easily discovered by reading a few lines of a file.

What happens to agent memory after context compaction?▼

After a compaction or context reset, the agent immediately calls cogni_session_summary to persist pre-compaction progress into SQLite, then calls cogni_context to restore active project context before continuing the task.