setup

setup is a command for Claude Code from joseairosa/recall. It costs 0 tokens per session (784 once invoked), scanned D, original, MIT.

A setup command for connecting Claude Code to Recall, a service that stores memory and provides searchable context across coding sessions. It saves the API key and server address in the configuration locations used by Recall hooks and the plugin connection.

In plain words
What is it for?
Use it to configure a Recall API key, choose the server URL, and prepare Claude Code's files for authenticated Recall access.
Why use it?
It prevents one part of the Recall integration from having credentials while another part does not. It also supports either the hosted Recall server or a self-hosted server.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions Claude Code.

Part of the recall plugin — 7 commands, 3 agents, 6 hooks shipped together

Good fit Use it to configure a Recall API key, choose the server URL, and prepare Claude Code's files for authenticated Recall access.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/joseairosa/recall/setup
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.

Clone the repo
git clone --depth 1 https://github.com/joseairosa/recall

Made for: Claude Code.

Or install recall, the plugin that ships this one along with the rest of its 7 commands, 3 agents, 6 hooks.

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 setup

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/joseairosa/recall/setup"><img src="https://agentmods.dev/badge/commands/joseairosa/recall/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 784 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 3 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00000 $0.00784
Opus 5.5 $0.00000 $0.00314
Sonnet 5.5 $0.00000 $0.00157
Haiku 4.5 $0.00000 $0.00078

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

Security

Grade D, and why

setup scanned grade D with 3 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

chmod 600 ~/.claude/recall/config.json

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat > ~/.claude/recall/config.json << EOF

Reads MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

- Three separate auth paths exist: hooks read from config.json via lib/config.sh; the plugin .mcp.json reads RECALL_API_KEY from settings.json env; ~/.claude.json is the authoritative runtime override for HTTP MCP server
claude-plugin/commands/setup.md · 74 lines

How it starts

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

Configure your Recall API key and server URL. This saves credentials to ~/.claude/recall/config.json (for hooks) and injects RECALL_API_KEY into ~/.claude/settings.json (for the plugin MCP server) so both systems authenticate correctly.

Instructions

  1. Ask the user for their Recall API key. It starts with sk- and can be found at https://recallmcp.com/dashboard/keys
  2. Ask if they want to use the default server (https://recallmcp.com) or a custom self-hosted URL
  3. Write the config file (used by lifecycle hooks via lib/config.sh):
mkdir -p ~/.claude/recall
cat > ~/.claude/recall/config.json << EOF
{
  "api_key": "THE_API_KEY",
  "server_url": "THE_SERVER_URL"
}
EOF
chmod 600 ~/.claude/recall/config.json
  1. Inject RECALL_API_KEY into ~/.claude/settings.json env section (belt-and-suspenders for hooks that read from env):
python3 - <<'PYEOF'
import json, os

settings_path = os.path.expanduser("~/.claude/settings.json")
with open(settings_path) as f:
    settings = json.load(f)

settings.setdefault("env", {})["RECALL_API_KEY"] = "THE_API_KEY"

with open(settings_path, "w") as f:
    json.dump(settings, f, indent=2)

print("RECALL_API_KEY written to settings.json env section")
PYEOF
  1. Update ~/.claude.json so the authoritative runtime config also has the new key. Claude Code reads ~/.claude.json as the final source for HTTP MCP server headers — if an entry for recall-remote already exists there, it bypasses the settings.json env var entirely:
python3 - <<'PYEOF'
import json, os

path = os.path.expanduser("~/.claude.json")
try:
    with open(path) as f:
        config = json.load(f)
except FileNotFoundError:
    config = {}

mcp = config.setdefault("mcpServers", {})
if "recall-remote" not in mcp:
    mcp["recall-remote"] = {"type": "http", "url": "THE_SERVER_URL/mcp", "headers": {}}
mcp["recall-remote"].setdefault("headers", {})["Authorization"] = "Bearer THE_API_KEY"

with open(path, "w") as f:
    json.dump(config, f, indent=2)

print("recall-remote updated in ~/.claude.json")
PYEOF
  1. Tell the user to restart Claude Code once — the MCP server reads env vars at launch, so the new key takes effect on next start.
  2. After restart, verify the connection by calling mcp__recall-remote__get_workspace. If it succeeds, Recall is working.
  3. Set up the workspace for the current project by calling set_workspace with the current directory and git remote.

Read the full file on GitHub · 74 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 · 74 lines · 0 tokens per session scan D 311183ee23d7

Subscribe to this mod's changes

setup is a command published in the GitHub repository joseairosa/recall (176 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 784 tokens. A static security scan graded it D with 3 findings (asks for root, reads agent configuration directories, reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.