Borrowing it
Nothing to install: this file belongs to ahmed3elshaer/everything-claude-code-mobile. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ahmed3elshaer/everything-claude-code-mobile/main/.opencode/skills/mobile-compaction/SKILL.mdgit 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-compaction)<a href="https://agentmods.dev/skills/ahmed3elshaer/everything-claude-code-mobile/mobile-compaction"><img src="https://agentmods.dev/badge/skills/ahmed3elshaer/everything-claude-code-mobile/mobile-compaction.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.00022 | $0.01399 |
| Opus 5 | $0.00011 | $0.00700 |
| Sonnet 5 | $0.00004 | $0.00280 |
| Haiku 4.5 | $0.00002 | $0.00140 |
Grade A, and why
mobile-compaction 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 4d 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Compaction Skill
Strategic context compaction for large Android projects to optimize token usage while preserving critical information.
When to Compact
Compact context when:
- Token usage exceeds 100,000
- Working on large refactors spanning many files
- Switching between unrelated features
- Session becomes unfocused
- Context contains resolved discussions
Compaction Strategies
1. Module-Level Compaction
Focus on a single Android module:
/compact --module=feature:auth
What happens:
- Retain: All files in feature:auth module
- Summarize: Other modules to high-level description
- Drop: Resolved discussions about other modules
Use when: Deep work on a specific feature
2. Layer-Based Compaction
Focus on architecture layer:
/compact --layer=ui
/compact --layer=data
/compact --layer=domain
What happens:
| Layer | Retain | Summarize |
|---|---|---|
| UI | Composables, ViewModels, navigation | Repository details, data models |
| Data | Repositories, data sources, models | Compose code, UI state |
| Domain | Use cases, domain models | Implementation details |
Use when: Working on cross-cutting concerns in a layer
3. Build Variant Focus
Narrow to specific build variant:
/compact --variant=debug
What happens:
- Retain: Debug-specific configurations, test code
- Summarize: Release configurations, ProGuard rules
Use when: Debugging or test development
4. Test Isolation
Compact around failing tests:
/compact --test=AuthViewModelTest
/compact --test-failing
What happens:
- Retain: Test file, related source files
- Summarize: Unrelated test discussions
- Drop: Resolved test fix discussions
Use when: Fixing specific test failures
5. Pattern-Based Compaction
Compact based on architectural patterns:
/compact --pattern=compose
/compact --pattern=mvi
/compact --pattern=koin
What happens:
- Retain: Files matching the pattern
- Summarize: Non-matching files to pattern names only
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.
- 4d ago First seen · 258 lines · 22 tokens per session scan A 0e71fff102e3
mobile-compaction is a skill published in the GitHub repository ahmed3elshaer/everything-claude-code-mobile (66 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 1,399 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.
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.
compose-performance
Use when investigating Jetpack Compose recomposition cost, compiler stability reports, skippability, unstable parameters, frame-rate State reads, cross-phase snapshot back-writing, or @ReadOnlyComposable contracts.