Save durable project knowledge to Mission Control's Recall (project memory) so future sessions start already knowing it, AND navigate this project's indexed code graph.

MITAuto-check passedAgent Workflows

Install Recall

skills CLI
$ npx skills add AgentSystemLabs/mission-control --skill recall -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AgentSystemLabs/mission-control recall --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AgentSystemLabs/mission-control.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/recall .claude/skills/recall && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
recall
GitHub stars
159
Token cost
~1.5k tokens
SKILL.md length
619 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

Save durable project knowledge to Mission Control's Recall (project memory) so future sessions start already knowing it, AND navigate this project's indexed code graph.

  • Decide something worth remembering about THIS project — an architecture fact
  • SKILL.md covers Navigating the code (Recall…, When to save a memory, How to save and Etiquette
  • Calls curl; needs MC_API_TOKEN
  • A decision and its rationale

What it does

Recall is an agent skill from AgentSystemLabs/mission-control. Save durable project knowledge to Mission Control's Recall (project memory) so future sessions start already knowing it, AND navigate this project's indexed code graph. Use when you discover or decide something worth remembering about THIS project — an architecture fact, a decision and its rationale, a convention, a stack detail, a glossary term, a known issue, or a useful discovery ("X lives in Y", "Z is generated"). Also use when you need to LOCATE or READ code — where a symbol is defined (and its verbatim…

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Agent memory and MCP servers. The licence is MIT.

When your agent uses it

  • Decide something worth remembering about THIS project — an architecture fact
  • A decision and its rationale
  • A glossary term
  • A useful discovery (X lives in Y

Example prompts

  • “X lives in Y”
  • “Z is generated”
  • “/recall”

Requirements

  • Python 3
  • A credential in MC_API_TOKEN

What it can do on your machine

Read from SKILL.md and the folder at commit 92b91d0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • MC_API_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Recall loads about 1.5k tokens when it runs. Until then it costs about 221 tokens; SKILL.md has 619 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~221
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AgentSystemLabs/mission-control at commit 92b91d0, republished under its MIT licence (© AgentSystemLabs). 619 words, ~1,477 tokens.

Download SKILL.mdSave it as .claude/skills/recall/SKILL.md (or your agent's skills folder).
name
recall
description
Save durable project knowledge to Mission Control's Recall (project memory) so future sessions start already knowing it, AND navigate this project's indexed code graph. Use when you discover or decide something worth remembering about THIS project — an architecture fact, a decision and its rationale, a convention, a stack detail, a glossary term, a known issue, or a useful discovery ("X lives in Y", "Z is generated"). Also use when you need to LOCATE or READ code — where a symbol is defined (and its verbatim source), what calls it, or what a change would impact — via the graph_search / graph_node / get_neighbors / impact_of / shortest_path MCP tools instead of grepping. Requires a Mission Control agent session (MC_API_URL, MC_API_TOKEN, MC_TASK_ID are injected automatically). Not for transient to-dos, run-specific notes, or projects running outside Mission Control.
user-invocable
true

Mission Control agent sessions receive env vars automatically:

  • MC_API_URL — loopback API base (e.g. http://127.0.0.1:54321)
  • MC_API_TOKEN — bearer token for that API
  • MC_TASK_ID — the active task/session id

Mission Control maintains Recall, a curated, per-project memory that it assembles into a Session Brief and hands to every new session. When you learn something durable about this project, write it back so the next session doesn't rediscover it.

Skip this entirely when the MC env vars are missing (plain shell outside Mission Control).

Navigating the code (Recall code graph)

Mission Control also indexes this project into a code graph — every function, class, method, type, interface, and file, plus the calls/imports between them. It's exposed as MCP tools on the recall server. Prefer these over grep/glob when you need to locate code or trace relationships — the graph is pre-indexed, ranked by how central a symbol is, and complete (it won't miss a dynamically-shaped call site the way a text search can):

  • graph_search(query, include_source?) — find where a symbol is defined by name or path (functions, classes, methods, types, React components, files). Your first move when you'd otherwise grep for a definition. Returns the most-connected matches first; pass include_source: true to get the top matches' verbatim source inline.
  • graph_node(node) — read a symbol's definition source (verbatim, line-numbered) without opening the file. Prefer this over Read when you need the body of one function/class/component.
  • get_neighbors(node, direction) — a symbol's direct callers/callees and importers. Answers "what calls X" / "what does X depend on" without grepping for call sites. direction: in, out, or both.
  • impact_of(node) — what transitively breaks if I change this (reverse-reachable dependents, several hops out). Run it before an edit instead of grepping for usages.
  • shortest_path(from, to) — how two areas connect through imports/calls — a question grep can't answer.

If a graph tool reports the project isn't indexed yet, fall back to grep for that lookup; don't block on it. The graph covers JavaScript/TypeScript (.ts / .tsx / .js / .jsx / .mts / .cts / .mjs / .cjs) and Python (.py).

Show full SKILL.md (295 more words)Show less

When to save a memory

Save a memory when you establish a durable fact about the project — not about the current task:

  • decision — a choice that was made and why ("Use JWT instead of session cookies — stateless across the worker fleet")
  • architecture — where things live / how data flows ("Auth flow lives in useAuth")
  • convention — a project-specific pattern or do/don't ("All API errors go through handleDomainError")
  • stack — a language/framework/build/runtime/infra fact
  • glossary — a domain term and its meaning
  • known-issue — a current limitation, gotcha, or flaky area
  • discovery — a useful finding ("Migrations run on boot from ensureSchema")
  • overview / preference — what the project is / how the user likes to work here

Do not save: the task you were asked to do, TODOs, transient state, or anything only true for this one run. Prefer a few high-signal facts over many. Recall dedupes by title, so re-saving a known fact is harmless.

How to save

First resolve the project id from the task, then POST the memory:

bash
# 1. Get the project id for this session.
PROJECT_ID=$(curl -s "$MC_API_URL/api/tasks/$MC_TASK_ID" \
  -H "authorization: Bearer $MC_API_TOKEN" \
  | sed -n 's/.*"projectId":"\([^"]*\)".*/\1/p')

# 2. Save a memory.
curl -s -X POST "$MC_API_URL/api/projects/$PROJECT_ID/memory" \
  -H "authorization: Bearer $MC_API_TOKEN" \
  -H "content-type: application/json" \
  -d '{
    "type": "decision",
    "title": "Use JWT instead of session cookies",
    "body": "Chosen for statelessness across the worker fleet.",
    "source": "agent",
    "confidence": "confirmed"
  }'
Fields
  • type (required) — one of overview, stack, architecture, decision, convention, glossary, known-issue, preference, discovery.
  • title (required) — a one-line headline. This is what gets injected into future briefs, so make it self-contained (≤ 200 chars).
  • body (optional) — a short detail: the why / where / how.
  • source — always send "agent" so the memory is tagged as agent-written.
  • confidence — "confirmed" when you verified it in the code, "inferred" when you're reasonably sure, "ambiguous" when unsure.
  • tags (optional) — a string array for filtering.

A 403 means the user has disabled agent memory writes in Settings → Recall — respect that and stop trying.

Etiquette

  • Save at most a handful of memories per session — the highest-signal facts only.
  • Keep each memory atomic (one fact per entry).
  • Don't echo the whole brief back; only write things that are genuinely new or now more certain.

© AgentSystemLabs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/recall of AgentSystemLabs/mission-control.

Open the folder on GitHubat commit 92b91d0

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in AgentSystemLabs/mission-control, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Recall next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Recall compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Recall this skillAgentSystemLabs/mission-control159—~1.5kAutomated safety check: PassMIT
MemPalace Setup and OperationMemPalace/mempalace59k—~2.2kAutomated safety check: PassMIT
agentmemory Setup and Diagnosticsrohitg00/agentmemory29k—~1kAutomated safety check: NotesApache-2.0
Qmdbreferrari/obsidian-mind4.9k—~1.7kAutomated safety check: PassMIT
Memori MCP Memory UsageMemoriLabs/Memori17k—~3.8kAutomated safety check: PassMIT
Shared Agent Knowledge Commonsmozilla-ai/cq1.3k—~6.5kAutomated safety check: PassApache-2.0

Similar skills

  • Installs and configures MemPalace as a private local palace, a shared-brain hub or a client of an existing hub, including MCP registration and version-correct initialization.

    59k GitHub stars~2.2k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Sets up and troubleshoots a local agentmemory install, covering the MCP connection, environment variables, ports, authentication and optional feature flags.

    29k GitHub stars~1k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes
  • Qmd

    breferrari/obsidian-mind

    Search the vault using QMD semantic search. An agent skill from breferrari/obsidian-mind.

    4.9k GitHub stars~1.7k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • Memori MCP Memory Usage

    MemoriLabs/Memori

    Teaches an MCP-connected agent when and how to call Memori's recall, summary, compaction, augmentation, feedback and quota tools to keep context across sessions.

    17k GitHub stars~3.8k tokensUpdated 5 days ago
    Agent WorkflowsAuto-check passed
  • Queries a shared knowledge store before acting, proposes newly discovered insights, and confirms or flags existing entries, so agents stop rediscovering the same failures.

    1.3k GitHub stars~6.5k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • Agent Recall

    Goldentrii/AgentRecall-X

    Persistent compounding memory for AI agents. An agent skill from Goldentrii/AgentRecall-X.

    371 GitHub stars~5.2k tokensUpdated 10 days ago
    Agent WorkflowsAuto-check: notes

More from AgentSystemLabs/mission-control

  • Diagram

    AgentSystemLabs/mission-control

    Show Mermaid diagrams in Mission Control's diagram viewer instead of dumping raw syntax in the terminal.

    159 GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • Release

    AgentSystemLabs/mission-control

    Cut a Mission Control desktop release — bump package.json (must match the git tag), commit, create an annotated v-tag, push to trigger release.yml CI.

    159 GitHub stars~1.3k tokensUpdated 16 days ago
    Auto-check passed

Categories

Questions about Recall

What does Recall do?

Save durable project knowledge to Mission Control's Recall (project memory) so future sessions start already knowing it, AND navigate this project's indexed code graph. Recall is an agent skill from AgentSystemLabs/mission-control. Save durable project knowledge to Mission Control's Recall (project memory) so future sessions start already knowing it, AND navigate this project's indexed code graph.

When should I use Recall?

Recall fits situations like: decide something worth remembering about THIS project — an architecture fact; A decision and its rationale; A glossary term; A useful discovery (X lives in Y.

How do I install Recall in Claude Code?

Run `npx skills add AgentSystemLabs/mission-control --skill recall -a claude-code`. Or copy the skill folder (.agents/skills/recall in AgentSystemLabs/mission-control) into .claude/skills/recall in your project. Claude Code loads it when a task matches its description.

How do I install Recall in Codex?

Run `npx skills add AgentSystemLabs/mission-control --skill recall -a codex`. Or copy the skill folder (.agents/skills/recall in AgentSystemLabs/mission-control) into .agents/skills/recall in your project. Codex loads it when a task matches its description.

Can I use Recall in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AgentSystemLabs/mission-control --skill recall -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/recall, .gemini/skills/recall, .github/skills/recall and .opencode/skills/recall in your project.

What does Recall need to run?

Going by SKILL.md and its folder, Recall needs the command-line tools its instructions call (curl) and credentials named MC_API_TOKEN. Our summary lists: Python 3; A credential in MC_API_TOKEN.

Does Recall access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Recall safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Recall use?

Recall is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Recall use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Recall?

Skills that share tags, products or a category with Recall: MemPalace Setup and Operation (MemPalace/mempalace, 59k stars), agentmemory Setup and Diagnostics (rohitg00/agentmemory, 29k stars), Qmd (breferrari/obsidian-mind, 4.9k stars) and Memori MCP Memory Usage (MemoriLabs/Memori, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Recall?

AgentSystemLabs (a GitHub organization) maintains it in AgentSystemLabs/mission-control, which has 159 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 22, 2026.

Source: AgentSystemLabs/mission-control on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.