memmesh-integrate

memmesh-integrate is a skill for Claude Code, Codex from ThinkfleetAI/memmesh. It costs 197 tokens per session (1,133 once invoked), scanned A, original, Apache-2.0.

An integration workflow for adding MemMesh, a memory system for coding agents, to an existing code repository. It detects the project's programming setup, uses TDD—writing tests before implementation—and supports hosted or local installations.

In plain words
What is it for?
Planning and implementing MemMesh in a repository, choosing between managed and local operation, and preparing tests and a reviewable change.
Why use it?
It reduces the risk of changing existing behavior while adding memory features. New code is additive and can be turned off with a feature flag.

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/thinkfleetai/memmesh/memmesh-integrate
Any agent
npx skills add ThinkfleetAI/memmesh --skill memmesh-integrate
Clone the repo
git clone --depth 1 https://github.com/ThinkfleetAI/memmesh

Made for: Claude Code, Codex.

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 memmesh-integrate

README.md
[![agentmods](https://agentmods.dev/badge/skills/thinkfleetai/memmesh/memmesh-integrate.svg)](https://agentmods.dev/skills/thinkfleetai/memmesh/memmesh-integrate)
Your own site
<a href="https://agentmods.dev/skills/thinkfleetai/memmesh/memmesh-integrate"><img src="https://agentmods.dev/badge/skills/thinkfleetai/memmesh/memmesh-integrate.svg" alt="Measured on agentmods" height="20"></a>
Per session 197 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,133 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.00197 $0.01133
Opus 5 $0.00098 $0.00566
Sonnet 5 $0.00039 $0.00227
Haiku 4.5 $0.00020 $0.00113

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

Security

Grade A, and why

memmesh-integrate 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 5d 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.

skills/memmesh-integrate/SKILL.md · 87 lines

How it starts

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

memmesh-integrate

Wire MemMesh into an existing repo with a goal-driven, test-first pipeline. Pairs with memmesh-test-integration for verification.

Canonical sources (fetch BEFORE deciding anything)

WebFetch these and cite them in plan.md. They are ground truth — do not rely on ambient knowledge of the API.

Integration principles (non-negotiable)

The goal is a PR the maintainers accept without argument.

  1. Additive, not replacing. If the repo already has a memory / session / user-context layer, MemMesh sits alongside it. The existing system keeps working unchanged.
  2. Opt-in by default. Gate all new code behind a flag (MEMMESH_ENABLED=1, a config key, or a strategy selector). Flag unset ⇒ original behavior, byte-for-byte.
  3. No breakage. No removed/renamed exports, no changed signatures, no modified existing tests. All pre-existing tests pass unchanged with the flag both set and unset.
  4. Minimal dependency surface. Add @thinkfleet/memory-sdk (hosted) or the memmesh binary (local) and nothing else.
  5. Separable commits. Code, tests, config/docs in separate commits.
  6. The null hypothesis wins. If no additive, gated fit exists, exit with a rationale. A bad PR is worse than no PR.
  7. Backend only. Integration lives in server-side code. Keys never ship to the client.

Pipeline

  1. Detect the stack (language, test runner, where user/session context is handled). Record in .memmesh-integration/detect.md.
  2. Choose surface — ask the user: Hosted (managed, mm- key, best for prediction/calibration/verticals) or Local (CLI + MCP over SQLite, no key, best for dev tools / offline). Default to Local for CLIs and dev tooling, Hosted for user-facing apps.
  3. Pick the seam. The highest-value seam is usually the request/response loop around the LLM: observe the user turn, search/buildContext before generating, and — where it adds value — predict the next action. Write the goal in plan.md and cite the canonical sources.
  4. Write failing tests first into .memmesh-integration/ and the repo's test dir: (a) flag-off ⇒ behavior unchanged; (b) flag-on ⇒ observe is called with the user turn; (c) flag-on ⇒ retrieved context reaches the prompt.
  5. Implement the smallest gated wiring that makes the tests pass. Delegate call-site patterns to memmesh-sdk / memmesh-cli.
  6. Consider the moat. If the app makes a decision about a user/account (offer, routing, retention), add an optional predict / predictTarget call and surface the calibrated confidence + abstention. Never let an abstention crash the flow — treat "I don't know yet" as a first-class branch.
  7. Emit artifacts in .memmesh-integration/ (detect.md, plan.md, changes.md, seed test data) and stop. Then run memmesh-test-integration.

Read the full file on GitHub · 87 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. 5d ago First seen · 87 lines · 197 tokens per session scan A 6f0be50eb9b9

Subscribe to this mod's changes

memmesh-integrate is a skill published in the GitHub repository ThinkfleetAI/memmesh (441 stars, last pushed 10d ago), licensed Apache-2.0. It adds 197 tokens to every session and 1,133 once invoked, about $0.0010 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.