memos-cloud-server

A connection to MemOS Cloud, an online long-term memory and knowledge-base service for storing and retrieving information across conversations.

In plain words
What is it for?
Use it to search, save, correct, or delete memories and manage knowledge bases and their documents, subject to the required API settings.
Why use it?
It lets an agent search earlier memories and user details instead of relying only on the current conversation.

Skill for Claude CodeCodex

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 skills/memtensor/memos-cloud-skill/memos-cloud-server
Any agent
npx skills add MemTensor/MemOS-Cloud-Skill --skill memos-cloud-server
Clone the repo
git clone --depth 1 https://github.com/MemTensor/MemOS-Cloud-Skill

Made for: Claude Code, Codex.

Per session 148 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,362 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.00148 $0.04362
Opus 5 $0.00074 $0.02181
Sonnet 5 $0.00030 $0.00872
Haiku 4.5 $0.00015 $0.00436

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

Security

Grade A, and why

memos-cloud-server 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.

The scan reads SKILL.md. This mod also ships 9 executable files (scripts/memos_cloud.py, scripts/memos_cloud/__init__.py, scripts/memos_cloud/cli.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

memos-cloud-server/SKILL.md · 354 lines

How it starts

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

MemOS Cloud Server Skill

This skill allows the Agent to interact with MemOS Cloud APIs for memory search, addition, deletion, knowledge base management, and feedback.

⚠️ Setup & Safety Rules (MUST READ)

Before executing any API operations, ensure these environment variables are configured. Each variable has an ownership layer — who is responsible for setting it — which determines whether it should ever be overridden at call time.

Variable Required Ownership layer Per-call override? Notes
MEMOS_API_KEY Yes User / deployment secret No Auth token. Never expose to the LLM.
MEMOS_USER_ID Yes User / host platform No Must be deterministic (hashed email, employee ID). Do NOT use random or per-session IDs.
MEMOS_CLOUD_URL No Deployment No API base URL. Default: https://memos.memtensor.cn/api/openmem/v1.
MEMOS_AGENT_ID No Host platform (per-process injection) Yes — via --agent-id on add_message / add_feedback Isolates memories per agent. A single global env var only supports one agent per machine; for multi-agent on one device, either let the host platform inject this per-process or pass --agent-id per call.
MEMOS_APP_ID No Host platform Yes — via --app-id on add_message / add_feedback Isolates memories per application. Same multi-tenant caveat as MEMOS_AGENT_ID.
MEMOS_ALLOW_PUBLIC No Admin / security policy No true/false, default false. Security boundary — never let the LLM toggle this per call.
MEMOS_ASYNC_MODE No Deployment No true/false, default true. Whether add_message returns before processing completes.

Multi-agent isolation pattern: Prefer per-process env injection by the host platform (each agent gets its own process tree with a distinct MEMOS_AGENT_ID). When the platform cannot inject env vars, fall back to passing --agent-id / --app-id on each call — the CLI flag takes precedence over the env var. These values must come from the orchestrator/platform; the LLM must not invent them.

Read the full file on GitHub · 354 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. yesterday First seen · 354 lines · 148 tokens per session scan A 9a010c0ffe3e

Subscribe to this mod's changes

memos-cloud-server is a skill published in the GitHub repository MemTensor/MemOS-Cloud-Skill (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 148 tokens to every session and 4,362 once invoked, about $0.0007 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens