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 skills add cdeust/Cortex --skill cortex-navigate-knowledgegit clone --depth 1 https://github.com/cdeust/CortexWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/cdeust/cortex/cortex-navigate-knowledge)<a href="https://agentmods.dev/skills/cdeust/cortex/cortex-navigate-knowledge"><img src="https://agentmods.dev/badge/skills/cdeust/cortex/cortex-navigate-knowledge/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cdeust/cortex/cortex-navigate-knowledge"><img src="https://agentmods.dev/badge/skills/cdeust/cortex/cortex-navigate-knowledge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What 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.1 | $0.00095 | $0.00780 |
| Opus 5.5 | $0.00038 | $0.00312 |
| Sonnet 5.5 | $0.00019 | $0.00156 |
| Haiku 4.5 | $0.00010 | $0.00078 |
Grade A, and why
cortex-navigate-knowledge 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 1mo ago.
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Navigate Knowledge — Graph Exploration and Causal Chains
Keywords
knowledge graph, relationships, connections, causal chain, how are these related, what connects, drill down, explore, navigate, entity graph, trace, cause and effect, related to, linked to, co-access, cluster
Overview
Cortex maintains a knowledge graph of entities (people, technologies, concepts, files) and their relationships extracted from memories. This skill lets you traverse that graph — follow causal chains, explore co-access patterns, drill into fractal memory clusters, and understand how different pieces of knowledge connect.
Use this skill when: You need to understand relationships between concepts, trace cause-and-effect chains, or explore a topic area systematically.
Workflow
Step 1: Trace Causal Chains
Follow entity relationships through the knowledge graph:
cortex:get_causal_chain({
"entity": "PostgreSQL",
"direction": "both",
"max_depth": 3
})
Returns a chain of entities connected by typed relationships (causes, uses, depends_on, related_to, etc.). Direction can be "forward" (effects), "backward" (causes), or "both".
Step 2: Navigate Co-Access Paths
Find memories frequently accessed together using Successor Representation:
cortex:navigate_memory({
"memory_id": <starting_memory_id>,
"depth": 2,
"max_nodes": 20
})
Returns a graph of memories connected by co-access frequency — revealing implicit relationships that aren't in the explicit knowledge graph.
Step 3: Hierarchical Exploration
Browse memories through fractal clusters (L0 = broad, L1 = mid, L2 = specific):
cortex:recall_hierarchical({
"query": "authentication system",
"levels": 3
})
Then drill into any interesting cluster:
cortex:drill_down({
"cluster_id": "<cluster from hierarchical recall>",
"level": "L1"
})
Step 4: Detect Structural Gaps
Find disconnected or under-connected areas:
cortex:detect_gaps({
"domain": "<optional>"
})
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.
- 1mo ago First seen · 102 lines · 95 tokens per session scan A 5b78d8c62153
cortex-navigate-knowledge is a skill published in the GitHub repository cdeust/Cortex (75 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 780 once invoked, about $0.0004 per session on Opus 5.5. 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-30.
Other skills, from other repositories
xmemo-memory
Persistent, user-owned memory for agents. Use the standalone runtime to remember, recall, search, preserve restart continuity, manage TODOs and expenses, inspect account overview, activity and stats diagnostics, or diagnose XMemo when MCP tools are unavailable. Not for codebase search, web search, or short-lived…
knowledge-audit
Review and clean up stored memories — find duplicates, contradictions, stale entries, and consolidate.
temporal-query
Answer time-travel questions over stored memory — what was believed at a past point in time, when a belief changed, and what replaced it. Use when the user says "as of", "back in", "at the time", "history of", "timeline", "what did I think then", or asks why a current memory contradicts an older one.
memory-commit
Use when the user explicitly says "remember this", "save this", "ghi nho", "luu lai", "save for next time", or otherwise asks to persist the immediately preceding context. Captures with the appropriate contexttype (decision, preference, fact, skill, task, conversation) so future sessions can retrieve it accurately.
recall-context
Use at session start, before significant decisions, or when a new task references a known project to recall mnemo memories matching the current working directory, recently edited files, or topic keywords. Helps maintain continuity across sessions and avoid redoing past research.
passport-bootstrap
Use when the user installs mnemo-mcp on a fresh machine and wants to restore prior memory state from S3 or Google Drive (Phase 2 passport sync). Triggers on phrases like "set up mnemo on this machine", "restore my memory passport", "import passport", "bootstrap mnemo", or when the user says they got a new laptop / VM…