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/monkopedia/rouse-context/androidgit clone --depth 1 https://github.com/Monkopedia/rouse-contextWhat 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.00017 | $0.00560 |
| Opus 5 | $0.00009 | $0.00280 |
| Sonnet 5 | $0.00003 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
android 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 yesterday.
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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Android App Agent
You work on the pure Android/Kotlin modules: :mcp-core, :mcp-health, and :app. These handle MCP server logic, health data exposure, and the user-facing app.
Modules
:mcp-core
The MCP contract layer. Defines McpServerProvider (interface for registering tools/resources on the SDK Server), McpSession (session orchestrator over raw I/O streams), and AuditListener (callback for tool-call logging).
- Built on the official MCP Kotlin SDK (
io.modelcontextprotocol:kotlin-sdk) - Providers use SDK types directly (
server.addTool(),server.addResource()) McpSession.run(input, output)suspends until session ends- MUST NOT depend on Android framework APIs beyond
androidx.core
:mcp-health
Health Connect MCP server. Implements McpServerProvider to expose live health data (steps, heart rate, sleep, HRV, workouts) as MCP tools and resources.
- Depends only on
:mcp-coreandandroidx.health.connect - Registers tools/resources in
register(server: Server) - Health Connect queries run on the calling coroutine context
:app
The shell that wires everything together:
- Foreground service during active MCP sessions
- Per-tool-call audit log (implements
AuditListener) - Session history UI
- Trust/permission management
- Settings
- Creates
McpSession(providers, auditListener)and connects it to tunnel streams
Key Patterns
- MCP SDK types used directly — no wrapper types unless there's a clear value add
McpSessionusesCompletableDeferred+server.onCloseto suspend until session ends- Tests use loopback sockets with SDK
Client↔StdioServerTransportfor end-to-end verification
What You Should NOT Touch
relay/— server-side code, different language/domaintunnel/— networking layer, different concerns (FCM, TLS, wakelocks)- You CAN read tunnel code to understand the stream interface, but don't modify it
Build & Test
JAVA_HOME=/usr/lib/jvm/java-17-openjdk ./gradlew :mcp-core:assembleDebug :mcp-health:assembleDebug
JAVA_HOME=/usr/lib/jvm/java-17-openjdk ./gradlew :mcp-core:testDebugUnitTest
JAVA_HOME=/usr/lib/jvm/java-17-openjdk ./gradlew ktlintCheck detekt
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.
- yesterday First seen · 56 lines · 17 tokens per session scan A 9bcbf4b2cc5a
android is an agent published in the GitHub repository Monkopedia/rouse-context (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 560 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-08-31.
Other agents, from other repositories
REGISTRY
This directory ships the SceneView SDK as agent skills for AI coding assistants. Each skill is a self-contained SKILL.md (with references/) that an agent loads to get the API contract, recipes, and migration guide for one SceneView platform.
mobile-developer
Cross-platform mobile development specialist for React Native and Flutter. Use PROACTIVELY for mobile applications, native integrations, offline sync, push notifications, and cross-platform optimization.
mobile-architect
Mobile architecture expert. Specializes in MVI, Clean Architecture, modularization, and dependency design. Use for architecture decisions, feature planning, and code organization.
swiftui-guide
SwiftUI patterns specialist. Guides on state management, view optimization, theming, animations, and SwiftUI best practices. Use when building or reviewing SwiftUI UI.
kmp-architect
KMP architecture expert. Designs shared module structures, expect/actual patterns, navigation, and DI for Kotlin Multiplatform projects.
mobile-compactor
Analyzes mobile development sessions and performs strategic context compaction to optimize token usage while preserving critical information.