setup

A setup command that connects the coding agent to Walrus Memory, a service for saving and finding project context. It checks whether the connection works and guides you through browser-based wallet login when needed.

In plain words
What is it for?
Use it when first connecting Walrus Memory or when you need to answer an additional setup question.
Why use it?
It removes the manual work of connecting the memory service and checking whether its tools are available.

Command

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.

agentmods
npx agentmods add commands/commandosslabs/walrus-memory-mcp-plugin/setup
Clone the repo
git clone --depth 1 https://github.com/CommandOSSLabs/walrus-memory-mcp-plugin
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 110 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00012 $0.00110
Opus 5 $0.00006 $0.00055
Sonnet 5 $0.00002 $0.00022
Haiku 4.5 $0.00001 $0.00011

Measured yesterday against content hash 9e3efca77f15, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

commands/setup.md · 16 lines

What it actually says

Use the Walrus Memory setup skill and MCP tools to connect this client.

First call memwal_health if the tool is available. If credentials are missing, call memwal_login and guide the user through the browser wallet flow. After login, verify with memwal_health.

If $ARGUMENTS is not empty, address this setup question too:

$ARGUMENTS
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. yesterday First seen · 16 lines · 12 tokens per session scan A 9e3efca77f15

Subscribe to this mod's changes

setup is a command published in the GitHub repository CommandOSSLabs/walrus-memory-mcp-plugin (0 stars, last pushed 12d ago), licensed Apache-2.0. It adds 12 tokens to every session and 110 once invoked, about $0.0001 per session on Opus 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-31.