What is scenario-player?

An agent that replays Android user-interface scenarios by executing their recorded actions on a device in sequence.

It runs a scenario file, optionally validates interface state or takes screenshots, controls timing and timeouts, and produces a replay report.

It checks whether a recorded flow still works and records which actions passed, failed, or needed retries.

How manuelsiuro/mcp-android-server-python configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to manuelsiuro/mcp-android-server-python. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/manuelsiuro/mcp-android-server-python/main/.claude/commands/agents/scenario-player.md

Clone the repo

git clone --depth 1 https://github.com/manuelsiuro/mcp-android-server-python

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/manuelsiuro/mcp-android-server-python/scenario-player/github.svg)](https://agentmods.dev/agents/manuelsiuro/mcp-android-server-python/scenario-player)

Your own site

<a href="https://agentmods.dev/agents/manuelsiuro/mcp-android-server-python/scenario-player"><img src="https://agentmods.dev/badge/agents/manuelsiuro/mcp-android-server-python/scenario-player/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/manuelsiuro/mcp-android-server-python/scenario-player"><img src="https://agentmods.dev/badge/agents/manuelsiuro/mcp-android-server-python/scenario-player.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 638 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.00638
Opus 5.5	$0.00000	$0.00255
Sonnet 5.5	$0.00000	$0.00128
Haiku 4.5	$0.00000	$0.00064

Measured 2mo ago against content hash 8eab2e0adb01, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

scenario-player 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 2mo 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.

.claude/commands/agents/scenario-player.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ScenarioPlayer Agent

You are a ScenarioPlayer Agent, specialized in orchestrating Android UI scenario replay.

Role

Primary agent that loads scenarios, executes actions in sequence, handles errors/retries, and generates comprehensive replay reports.

Inputs

scenario_file: (required) Path to scenario JSON file
device_id: (optional) Target Android device ID
config: (optional) Replay configuration:
- validate_ui_state: bool (default: false)
- take_screenshots: bool (default: false)
- continue_on_error: bool (default: false)
- speed_multiplier: float (default: 1.0) - Adjust delay timing
- timeout_multiplier: float (default: 1.0) - Adjust timeouts

Processing Steps

Outputs

{
  "replay_id": "uuid-string",
  "status": "PASSED" | "FAILED" | "PARTIAL",
  "duration_ms": 12000,
  "actions_total": 10,
  "actions_passed": 10,
  "actions_failed": 0,
  "report_file": "reports/replay_20250115_103000_abc123.json",
  "action_results": [
    {
      "action_id": 0,
      "status": "PASSED",
      "execution_time_ms": 1200,
      "error": null,
      "retry_count": 0
    }
  ]
}

Implementation

from agents.replay import ScenarioPlayerAgent

agent = ScenarioPlayerAgent()
result = agent.execute({
    "scenario_file": "scenarios/login_flow/scenario.json",
    "device_id": "emulator-5554",
    "config": {
        "continue_on_error": False,
        "speed_multiplier": 1.0
    }
})

Read the full file on GitHub · 84 lines

Changes

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.

2mo ago First seen · 84 lines · 0 tokens per session scan A 8eab2e0adb01

Subscribe to this mod's changes

scenario-player is an agent published in the GitHub repository manuelsiuro/mcp-android-server-python (0 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 638 tokens. 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.

E2E testing Mobile Testing

gem-mobile-tester

Mobile E2E testing: Detox, Maestro, iOS/Android simulators.

github/awesome-copilot · 22 tokens

rn-pr-qa

Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…

Lykhoyda/rn-dev-agent · 299 tokens

testing-specialist

Swift testing expert. Covers Swift Testing framework (@Test, @Suite, #expect), XCTest, UI testing, mocking patterns, testable architecture, snapshot testing, code coverage, and deterministic async testing.

The-Artificer-of-Ciphers-LLC/skills-from-the-artificer · 44 tokens

android-emulator-tester

Automated Android UI/integration testing specialist; the agent that drives a real Android app on a headless emulator under WSL/Linux and gates on what it observes. Use when the task is "run the app on an emulator", "smoke-test a screen", "drive the Android UI", "reproduce a tap-and-crash / ANR", "automate an Android…

simiancraft/simiancraft-skills · 247 tokens

mobile-tester

Tests a Flutter or mobile app like a real user on an Android AVD or iOS simulator, verifying with parsed screenshots and integration tests. - Use when an app build needs a real run on an emulator or simulator, with screenshots as evidence. Read-only on source; reports pass/fail with evidence paths. Spawn one per app…

uwuclxdy/agenticat · 73 tokens

mobile-mobile-qa

Mobile QA engineer that tests mobile applications, performs device testing, and ensures quality.

MonumentalSystems/Atlas-Agent-Teams · 20 tokens

mcp-android-server-python: Agent for Claude Code