cortex-recall-global

cortex-recall-global is a skill for Claude Code from cdeust/Cortex. It costs 86 tokens per session (735 once invoked), scanned A, original, MIT.

A skill for searching shared Cortex memories that apply across projects. These memories can include coding standards, infrastructure details, security policies, and team agreements.

In plain words
What is it for?
Use it to check organization-wide conventions, shared technical decisions, infrastructure facts, security rules, or other cross-project guidance.
Why use it?
It helps an AI assistant find rules and knowledge that are not limited to the current project.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the hypermnesia-mcp plugin — 13 skills, 3 commands, 2 MCP servers shipped together

Good fit Use it to check organization-wide conventions, shared technical decisions, infrastructure facts, security rules, or other cross-project guidance.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cdeust/cortex/cortex-recall-global
Install

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.

Any agent
npx skills add cdeust/Cortex --skill cortex-recall-global
Clone the repo
git clone --depth 1 https://github.com/cdeust/Cortex

Made for: Claude Code.

Or install hypermnesia-mcp, the plugin that ships this one along with the rest of its 13 skills, 3 commands, 2 MCP servers.

Wrote 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.

agentmods badge for cortex-recall-global

README.md
[![agentmods](https://agentmods.dev/badge/skills/cdeust/cortex/cortex-recall-global/github.svg)](https://agentmods.dev/skills/cdeust/cortex/cortex-recall-global)
Your own site
<a href="https://agentmods.dev/skills/cdeust/cortex/cortex-recall-global"><img src="https://agentmods.dev/badge/skills/cdeust/cortex/cortex-recall-global/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.

agentmods 80×15 button for cortex-recall-global

Your own site · 80×15
<a href="https://agentmods.dev/skills/cdeust/cortex/cortex-recall-global"><img src="https://agentmods.dev/badge/skills/cdeust/cortex/cortex-recall-global.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 735 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00086 $0.00735
Opus 5.5 $0.00034 $0.00294
Sonnet 5.5 $0.00017 $0.00147
Haiku 4.5 $0.00009 $0.00073

Measured 1mo ago against content hash b54e802ab488, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cortex-recall-global 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.

skills/cortex-recall-global/SKILL.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Recall Global — Retrieve Cross-Project Knowledge

Keywords

global, convention, standard, rule, infrastructure, policy, all projects, shared, universal, what's our rule, coding standard, architecture rule, team agreement, cross-project, server config, deployment

Overview

Retrieve global memories — knowledge stored as cross-project that's visible regardless of which project you're currently working in. Global memories include architecture rules, coding conventions, infrastructure facts, security policies, and team agreements.

Note: Regular cortex:recall already surfaces global memories automatically. This skill is for when you specifically want to focus on cross-project knowledge.

Workflow

Step 1: Recall Global Knowledge

Query with any domain — global memories appear alongside domain-specific results:

cortex:recall({
  "query": "<topic to search for>",
  "max_results": 10
})

Global memories are included in results regardless of the current project domain.

Step 2: Filter to Global Only

To see only global cross-project knowledge, use the unified neural graph:

cortex:open_visualization()

Click the Global filter button (pink) to isolate all global memories.

Click the Global filter — global memories appear as pink nodes connected to all project domains.

Step 3: Explore by Category

Common global recall patterns:

Architecture rules:

cortex:recall({ "query": "architecture rules and principles" })

Infrastructure:

cortex:recall({ "query": "server addresses and database connections" })

Coding conventions:

cortex:recall({ "query": "coding standards and naming conventions" })

Security policies:

cortex:recall({ "query": "security policies and credential management" })

Step 4: Navigate Connections

After finding a global memory, explore what it connects to across projects:

cortex:navigate_memory({
  "memory_id": <id>,
  "depth": 2
})

Global memories link to all domain hubs in the knowledge graph — following connections shows which projects reference similar concepts.

Read the full file on GitHub · 97 lines

Changes

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.

  1. 1mo ago First seen · 97 lines · 86 tokens per session scan A b54e802ab488

Subscribe to this mod's changes

cortex-recall-global is a skill published in the GitHub repository cdeust/Cortex (75 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 735 once invoked, about $0.0003 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.

Related

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…

yonro/memory-os-cli · 68 tokens

knowledge-audit

Review and clean up stored memories — find duplicates, contradictions, stale entries, and consolidate.

n24q02m/mnemo-mcp · 21 tokens

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.

n24q02m/mnemo-mcp · 77 tokens

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.

n24q02m/mnemo-mcp · 72 tokens

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.

n24q02m/mnemo-mcp · 53 tokens

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…

n24q02m/mnemo-mcp · 83 tokens