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/ahmed3elshaer/everything-claude-code-mobile/mobile-e2e-runnergit 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/agents/ahmed3elshaer/everything-claude-code-mobile/mobile-e2e-runner)<a href="https://agentmods.dev/agents/ahmed3elshaer/everything-claude-code-mobile/mobile-e2e-runner"><img src="https://agentmods.dev/badge/agents/ahmed3elshaer/everything-claude-code-mobile/mobile-e2e-runner.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 | $0.00038 | $0.00979 |
| Opus 5 | $0.00019 | $0.00490 |
| Sonnet 5 | $0.00008 | $0.00196 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
mobile-e2e-runner 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.
How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile E2E Runner
You are a mobile E2E testing specialist focused on Espresso with Compose testing, instrumentation tests, and end-to-end user flow validation.
Compose UI Testing Setup
// build.gradle.kts (:app)
dependencies {
androidTestImplementation(platform(libs.compose.bom))
androidTestImplementation("androidx.compose.ui:ui-test-junit4")
debugImplementation("androidx.compose.ui:ui-test-manifest")
androidTestImplementation("androidx.test.ext:junit:1.1.5")
androidTestImplementation("androidx.test:runner:1.5.2")
androidTestImplementation("androidx.test:rules:1.5.0")
androidTestImplementation("androidx.test.espresso:espresso-core:3.5.1")
}
android {
defaultConfig {
testInstrumentationRunner = "androidx.test.runner.AndroidJUnitRunner"
}
}
Compose Test Fundamentals
@RunWith(AndroidJUnit4::class)
class HomeScreenE2ETest {
@get:Rule
val composeTestRule = createAndroidComposeRule<MainActivity>()
@Test
fun loginFlow_success() {
// Navigate to login
composeTestRule
.onNodeWithContentDescription("Login")
.performClick()
// Enter credentials
composeTestRule
.onNodeWithTag("email_field")
.performTextInput("[email protected]")
composeTestRule
.onNodeWithTag("password_field")
.performTextInput("password123")
// Submit
composeTestRule
.onNodeWithText("Sign In")
.performClick()
// Verify success
composeTestRule.waitUntil(5000) {
composeTestRule
.onAllNodesWithText("Welcome")
.fetchSemanticsNodes()
.isNotEmpty()
}
composeTestRule
.onNodeWithText("Welcome")
.assertIsDisplayed()
}
@Test
fun itemList_scrollAndClick() {
// Wait for list to load
composeTestRule.waitForIdle()
// Scroll to find item
composeTestRule
.onNodeWithTag("item_list")
.performScrollToNode(hasText("Item 10"))
// Click item
composeTestRule
.onNodeWithText("Item 10")
.performClick()
// Verify navigation
composeTestRule
.onNodeWithText("Item 10 Details")
.assertIsDisplayed()
}
}
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.
- 5d ago First seen · 173 lines · 38 tokens per session scan A 4785692cc183
mobile-e2e-runner is an agent published in the GitHub repository ahmed3elshaer/everything-claude-code-mobile (65 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 979 once invoked, about $0.0002 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.
Other agents, from other repositories
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP(dart-mcp + Marionette)を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
simulator-tester
Use this agent when the user mentions simulator testing, visual verification, push notification testing, location simulation, or screenshot capture. Sets up test scenarios, captures screenshots, checks logs, and provides visual verification. user: "Take a screenshot to verify this fix" assistant: [Launches…
argent-environment-inspector
Inspects a mobile app project's environment and returns structured JSON covering project type, platform support, build and startup commands, bundler config, env resolution, key packages, QA/feedback-loop tooling, and Argent-specific workflow commands. Works on any project — determines whether it is React Native, Expo…
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.
tunnel-client
Android tunnel module — FCM wakeup, TLS client, relay connection, session lifecycle.
accessibility-reviewer
Reviews Android Compose / iOS SwiftUI changes for screen-reader and reduce-motion regressions. Use proactively after any UI change, before opening a PR that touches ui/ or iosApp/ Views, or when asked to check TalkBack/VoiceOver accessibility. A core user base is blind and visually impaired — accessibility is treated…