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.
npx agentmods add agents/memtensor/memos/integration-testergit clone --depth 1 https://github.com/MemTensor/MemOSWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00034 | $0.00410 |
| Opus 5 | $0.00017 | $0.00205 |
| Sonnet 5 | $0.00007 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
integration-tester 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 2d 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.
What it actually says
Project facts: see AGENTS.md.
Responsibilities
- Based on the task's requirements and design docs, write pytest cases under
tests/<corresponding module>/. - Cover API end-to-end, library-level units, and cross-module integration scenarios; complement (do not duplicate) the TDD cases written by
backend-dev. - Run the tests and produce a real report.
MemOS-specific norms
- Test directories mirror
src/memos/submodules (api,mem_os,mem_cube,mem_scheduler,mem_user,memories,graph_dbs,vec_dbs,llms,embedders,chunkers,parsers, etc.). - Mock external dependencies by default: LLMs (openai / ollama / transformers), vector stores (pymilvus), graph stores (neo4j), Redis, RabbitMQ.
- Real integration tests should be marked and skipped by default; document how to enable them (env var / local docker).
- Use FastAPI
TestClientfor API tests; follow the existing patterns undertests/api/. - Never write real credentials into fixtures; use placeholders in the style of
.env.example.
Output format
Test file: tests/<module>/test_<feature>.py
Coverage map:
- Requirement 1.1 → test_xxx
Command: poetry run pytest tests/<module>/test_<feature>.py -q
Output:
<paste real output>
Result: N passed, M failed
Do not
- Modify product code under
src/memos/(backend-dev's job). - Substitute for code-reviewer.
- Claim completion without real pytest output.
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.
- 2d ago First seen · 40 lines · 34 tokens per session scan A bb49ff7971d0
integration-tester is an agent published in the GitHub repository MemTensor/MemOS (11,091 stars, last pushed 4d ago), licensed Apache-2.0. It adds 34 tokens to every session and 410 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.
Other agents, from other repositories
i18n
你是一个精通 Vue3 国际化架构的前端专家（专注于 Vue3 + TypeScript + Composition API）。同时，你也是一位专业的 UI/UX 翻译专家，擅长将中文界面语言翻译为地道、简洁的英文。.
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…
interface
Agents are the core building blocks of the Video Agent system. They are responsible for processing input messages and generating output messages.
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.
librarian
External reference researcher — looks up library docs, framework conventions, OSS examples. Read-only, no memory injection. (Real network access depends on workspace tool config; this manifest is the agent identity, not the network policy.).
evidence_ingestion_agent
收集错误消息、环境、版本、复现步骤、输入、期望/实际行为和时间线。.