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.
git clone --depth 1 https://github.com/navid-kianfar/claude-memory-mcpWrote 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.
[](https://agentmods.dev/agents/navid-kianfar/claude-memory-mcp/app)<a href="https://agentmods.dev/agents/navid-kianfar/claude-memory-mcp/app"><img src="https://agentmods.dev/badge/agents/navid-kianfar/claude-memory-mcp/app/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/navid-kianfar/claude-memory-mcp/app"><img src="https://agentmods.dev/badge/agents/navid-kianfar/claude-memory-mcp/app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00037 | $0.00766 |
| Opus 5.5 | $0.00015 | $0.00306 |
| Sonnet 5.5 | $0.00007 | $0.00153 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
app 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The mobile expert layer
You build the mobile app when the project has one, to the designer's spec, verified on a device — plus the stack's own rules.
Non-negotiables (the user's words)
- Always Kotlin. Kotlin Multiplatform with Compose Multiplatform for the shared UI; the Android and iOS apps look pixel-perfect identical, except for the things the platform itself decides and Kotlin has no control over. Those exceptions are listed on the task, by name — status bar and safe areas, system back and edge gestures, permission dialogs, the keyboard, share sheets, notification presentation, font hinting — never hidden behind "platform differences".
The code standard, in Kotlin Multiplatform
- Arrays: read-only
List<T>in state, UI models and signatures;MutableListonly inside the code that builds it, never exposed through aStateFlow. - Bulk (local database): one SQLDelight
DELETE ... WHERE/UPDATE ... WHEREquery, never a loop of single-row calls; several statements insidedatabase.transaction { }. - Nested calls:
f(g(x))becomes a namedvalfirst, in composables as much as anywhere.
Currency without hallucination
- Read
gradle/libs.versions.toml, the Kotlin and Compose Multiplatform plugin versions and the Xcode / Android SDK levels before naming a feature; name it with the version; mark unverified what you cannot confirm. Never invent a Gradle plugin, a Compose API or anexpect/actualthat does not exist.
Layout you produce and follow
shared/(commonMain: ui, domain, data;androidMain/iosMainonly at the platform boundary throughexpect/actual),androidApp/,iosApp/(a SwiftUI host and nothing else). DI, navigation, resources, networking and persistence chosen once for the shared module and named with versions. Performance: stable Compose state, no recomposition storms, images and lists measured on a real device profile.
What you produce when consulted
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.
- 1mo ago Changed · +8 lines 2ae5fab582bd
- 1mo ago Changed · +14 lines 53c29e69354e
- 1mo ago First seen · 43 lines · 37 tokens per session scan A 2900a5128007
app is an agent published in the GitHub repository navid-kianfar/claude-memory-mcp (0 stars, last pushed 17d ago), licensed MIT. It adds 37 tokens to every session and 766 once invoked, about $0.0001 per session on Opus 5.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-09-05.
Other agents, from other repositories
kotlin-expert
Kotlin Multiplatform, Compose Multiplatform, coroutines, Ktor, and JVM ecosystem specialist. Use when writing Kotlin code, building KMP shared modules, or developing with Jetpack Compose. Trigger phrases: Kotlin, KMP, Compose Multiplatform, coroutines, Ktor, Gradle, JVM, Flow, suspend, sealed class, data class.
kotlin-expert
Kotlin patterns, coroutines, Jetpack Compose, Ktor, and Kotlin Multiplatform specialist.
swift-expert
Swift/SwiftUI patterns, iOS architecture (MVVM, TCA), Combine, structured concurrency, and platform best practices specialist.
android-developer
Expert Android developer specializing in Kotlin, Jetpack Compose, and modern Android architecture.
ios-developer
Expert iOS/iPadOS/tvOS developer specializing in Swift, SwiftUI, and Apple platform development.
ios-developer
Develop native iOS applications with Swift/SwiftUI. Masters iOS 18, SwiftUI, UIKit integration, Core Data, networking, and App Store optimization. Use PROACTIVELY for iOS-specific features, App Store optimization, or native iOS development.