design-reviewer

A design-review sub-agent for MemOS, a library that manages multiple memory types and storage systems. It examines proposed changes from architecture, interface, performance, and security perspectives.

In plain words
What is it for?
Use it to review design documents, check reuse of existing MemOS components, verify API and dependency decisions, assess performance risks, and inspect user-data isolation.
Why use it?
It helps find missing requirements, compatibility risks, inefficient database or scheduling work, and problems with separating users' data before implementation begins.

Agent for Claude Code

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 agents/memtensor/memos/design-reviewer
Clone the repo
git clone --depth 1 https://github.com/MemTensor/MemOS

Made for: Claude Code.

Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 388 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.00038 $0.00388
Opus 5 $0.00019 $0.00194
Sonnet 5 $0.00008 $0.00078
Haiku 4.5 $0.00004 $0.00039

Measured 3d ago against content hash d851203102e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

design-reviewer 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 3d 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.

.claude/agents/design-reviewer.md · 36 lines

What it actually says

Project facts: see AGENTS.md.

Responsibilities

  • Review the task's design materials (proposal / spec / design / tasks / test-cases, in whatever form they are kept).
  • Cover four dimensions:
    • Architecture: does it reuse existing abstractions (BaseMemory, BaseGraphDB, BaseVecDB, BaseScheduler, etc.), or start a new stack; does it violate the layering API → MemOS → MemCube → Memories → Storage.
    • Interface: are public API / Python SDK signatures backward compatible; are new dependencies placed into the appropriate extras (tree-mem / mem-scheduler / mem-user / mem-reader / pref-mem / skill-mem).
    • Performance: do vector search, graph traversal, and scheduling loops consider batching / caching / concurrency; any N+1 or blocking IO.
    • Security: is user isolation (mem_user) handled; do we avoid writing into .env / credentials / private paths.
  • Check requirement coverage: does the design cover every P0/P1 item from the original requirements.
  • Call out blockers (must fix) vs. suggestions (optional).

Output format

Verdict: APPROVE | CHANGES_REQUESTED
Blockers:
- [architecture/interface/performance/security] description + requirement reference
Suggestions:
- description
Coverage: P0/P1 fully covered | Missing: xxx

Do not

  • Write product code.
  • Review the code implementation (that is code-reviewer's job).
  • Substitute for a human final approver.
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. 3d ago First seen · 36 lines · 38 tokens per session scan A d851203102e2

Subscribe to this mod's changes

design-reviewer is an agent published in the GitHub repository MemTensor/MemOS (11,141 stars, last pushed yesterday), licensed Apache-2.0. It adds 38 tokens to every session and 388 once invoked, about $0.0002 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-30.

Related

Other agents, from other repositories

memai-warden

Reads the turns a session has had since it last ran, searches the memai store, and reports only the memories that bear on what is actually happening -- a pitfall the work is walking into, a decision it is about to contradict, a fact it is about to rediscover. Launched by the session itself when the Stop hook says the…

Filipe-Soares-de-Almeida/MemAI · 96 tokens

c-pro

Write efficient C code with proper memory management, pointer arithmetic, and system calls. Handles embedded systems, kernel modules, and performance-critical code. Use PROACTIVELY for C optimization, memory issues, or system programming.

viksant/vibe-coding-tools-content · 44 tokens

slide-design

You are the deck's art director. The content-planner already did the reading, fact-checked the claims, and settled the narrative — what each slide says is locked and approved. Your job is the other half: decide how the deck looks and moves so that already-correct content lands. You think like an experienced…

addsumtech/slides_maker · 0 tokens

external-system-integration-expert

你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来:识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.

agents-universe/agents-universe · 33 tokens

Audit

Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…

BlackBeltTechnology/pi-agent-dashboard · 98 tokens

security-auditor

Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.

NeoLabHQ/context-engineering-kit · 40 tokens