Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/shawnhack/exocortex/publicnpx skills add shawnhack/exocortex --skill publicgit clone --depth 1 https://github.com/shawnhack/exocortexWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00478 |
| Opus 5 | $0.00000 | $0.00239 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
public scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
exocortex
Persistent long-term memory for AI agents. Store, search, and reason over knowledge that persists across sessions. Semantic search, knowledge graphs, temporal reasoning, and self-improving retrieval.
Tools
Core
memory_store— Store knowledge with content, tags, importance (0-1), tier, namespacememory_search— Hybrid search (vector + FTS + graph). Use expanded_query for better recall, compact for token efficiencymemory_get— Fetch full memory content by IDmemory_context— Load broad context for a topic. Use deep=true for LLM-driven iterative retrievalmemory_update— Update memory content, tags, importance, or metadatamemory_forget— Soft-delete a memory
Intelligence
memory_project_snapshot— Project context: goals, decisions, threads, techniquesmemory_contradictions— Find contradictory facts in stored knowledgememory_timeline— Track topic evolution over timememory_diff— Compare memory state between time periods
Knowledge Graph
memory_entities— Browse extracted entities (people, projects, tech)memory_graph— Entity relationship graph with centrality scoresmemory_link— Create explicit connections between memories
Ingestion
memory_ingest— Ingest documents/URLs with automatic chunkingmemory_research— Web research with automatic knowledge storage
Goals & Predictions
goal— Track goals with milestones and progressprediction— Make and resolve predictions for calibration
Usage Pattern
Session start:
memory_contextwith topic → load relevant backgroundmemory_project_snapshot→ goals, decisions, open threads
During work:
3. memory_search for specific knowledge retrieval
4. memory_store to persist decisions, discoveries, techniques
Session end: 5. Store session summary and key learnings
Authentication
Set auth.token in DB settings. Pass via Authorization: Bearer <token> or X-Exocortex-Token.
Links
- REST: http://localhost:4010
- MCP: stdio transport
- Dashboard: http://localhost:4010 (web UI)
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 54 lines · 0 tokens per session scan A 08d13b9ee729
public is a skill published in the GitHub repository shawnhack/exocortex (1 stars, last pushed 27d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 478 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
seller-research
Use when researching a merchant, storefront, marketplace seller, or merchant of record for a buying decision, especially when identity, refund terms, fulfillment, counterfeit risk, domain history, or independent buyer outcomes are uncertain.
product-research
Use when researching or comparing a specific product, model, or variant for a buying decision, especially when specifications conflict, fit or compatibility matters, retailer copy dominates, or the evidence may be incomplete.
uteke-memory
Persistent memory engine for AI agents via the uteke CLI — remember, recall, search, forget with semantic + FTS5 hybrid search, documents, knowledge graph, rooms, tiered memory, and multi-agent namespaces.
gno
Search local documents, files, notes, and knowledge bases. Index directories, search with BM25/vector/hybrid, get AI answers with citations. Use when user wants to search files, find documents, query notes, look up information in local folders, index a directory, set up document search, build a knowledge base, needs…
release-gatekeeper
End-to-end release validation for Connapse — the 'final boss' before any version ships. Downloads the latest alpha from GitHub Releases, deploys an isolated Docker instance (separate from production), then systematically tests every feature: UI via Playwright, API via curl/REST, MCP tools, search quality, security…
create-tickets
Batch-create GitHub issues from a brainstorming discussion. Decomposes ideas into properly-sized tickets with labels, milestones, and project board placement. Trigger when user says: create tickets, make tickets, turn ideas into issues, create issues from brainstorm, create issues from discussion, batch create issues.