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 skills/ahmed3elshaer/everything-claude-code-mobile/mobile-memorynpx skills add ahmed3elshaer/everything-claude-code-mobile --skill mobile-memorygit clone --depth 1 https://github.com/ahmed3elshaer/everything-claude-code-mobileWrote 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/skills/ahmed3elshaer/everything-claude-code-mobile/mobile-memory)<a href="https://agentmods.dev/skills/ahmed3elshaer/everything-claude-code-mobile/mobile-memory"><img src="https://agentmods.dev/badge/skills/ahmed3elshaer/everything-claude-code-mobile/mobile-memory.svg" alt="Measured on agentmods" 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.00025 | $0.01173 |
| Opus 5 | $0.00013 | $0.00587 |
| Sonnet 5 | $0.00005 | $0.00235 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
mobile-memory 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.
How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Memory Skill
Persistent memory system that maintains mobile development context across sessions.
Purpose
Unlike instincts (which capture patterns), memory retains factual project state:
- What modules exist
- What dependencies are installed
- What the architecture looks like
- What tests cover what code
This survives session breaks and compaction.
Memory Types
Project Structure Memory
Remembers your Android project layout:
{
"modules": ["app", "core:network", "feature:auth"],
"buildVariants": ["debug", "release", "staging"],
"featureModules": ["auth", "home", "profile"]
}
Use when: Starting work on a new feature, need to know project layout
Dependencies Memory
Tracks all Gradle dependencies:
{
"libraries": [
{"name": "compose-runtime", "group": "androidx.compose", "version": "1.5.0"}
],
"kgpVersion": "1.9.20",
"gradleVersion": "8.2"
}
Use when: Adding new dependencies, checking compatibility
Architecture Memory
Documents your architecture patterns:
{
"pattern": "mvi",
"uiLayer": {"screens": ["Home", "Profile"]},
"dataLayer": {"repositories": ["UserRepository"]},
"di": {"framework": "koin", "modules": ["appModule"]}
}
Use when: Onboarding new developers, explaining codebase
Test Coverage Memory
Tracks test metrics:
{
"totalCoverage": 78,
"trend": "improving",
"failingTests": [
{"class": "AuthViewModelTest", "method": "testLogin"}
]
}
Use when: Planning testing work, tracking quality goals
Compose Screens Memory
Indexes all Composable screens:
{
"screens": [
{"name": "HomeScreen", "route": "home", "file": "HomeScreen.kt"}
]
}
Use when: Finding screens, understanding navigation
Usage
Load Memory
# At session start - load all memory
/memory-load all
# Load specific type
/memory-load project-structure
/memory-load dependencies
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 · 218 lines · 25 tokens per session scan A 3ad62fb8b878
mobile-memory is a skill published in the GitHub repository ahmed3elshaer/everything-claude-code-mobile (65 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 1,173 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
SKILL
This document provides a comprehensive technical reference for KSensor, a Kotlin Multiplatform (KMP) library designed for observing device sensors and system states on Android and iOS.
mobile-mcp
Mobile automation and debugging for Android and iOS apps via accessibility snapshots. Use when asked to test, debug, inspect, screenshot, tap, swipe, type, navigate, or crash-report on the Livtet mobile apps. Triggers on "screen", "tap", "click", "screenshot", "debug on device", "what's on screen", "launch the app"…
compose-animations
Use when writing or reviewing Jetpack Compose motion: visibility enter/exit, animating one property toward a target, color or size transitions, multiple properties from one state, switching composable content, or choosing between AnimatedVisibility, animateAsState, rememberTransition, AnimatedContent, and Crossfade.
compose-focus-navigation
Use when writing or reviewing Jetpack Compose UI for TV, keyboard, desktop, accessibility focus, D-pad navigation, FocusRequester, focusProperties, key events, or initial focus behavior.
compose-state-and-effects
Use when writing or reviewing Jetpack Compose state ownership, remember state, state hoisting, screen state holders, LaunchedEffect, DisposableEffect, SideEffect, Flow collection, navigation, snackbar, analytics, or focus requests.
compose-component-design
Use when designing or reviewing reusable Jetpack Compose component APIs with modifier parameters, root layout placement, caller-provided variable content, primitive content parameters, optional content, or boolean shape flags.