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.

scenario-player — Agent by manuelsiuro

Install

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.

agentmods

npx agentmods add agents/manuelsiuro/mcp-android-server-python/scenario-player

Clone the repo

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

Made for: Claude Code.

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. Scan, not verified.

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	$0.00000	$0.00638
Opus 5	$0.00000	$0.00319
Sonnet 5	$0.00000	$0.00128
Haiku 4.5	$0.00000	$0.00064

Measured yesterday against content hash 8eab2e0adb01, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

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

yesterday 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 11mo 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.

Frontend Mobile

ux-flow-auditor

Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…

CharlesWiltgen/Axiom · 190 tokens

gem-mobile-tester

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

mubaidr/gem-team · 22 tokens

flutter-integration-analyzer

Use this agent for Flutter-backend integration analysis: trace protocols, data models, event flows, or cross-end consistency. Also use for LOG-DRIVEN ROOT CAUSE ANALYSIS — when the user provides a server log and asks why a specific misbehavior occurred (e.g. "why did it stop responding"), this agent parses the log…

JayCRL/MobileVC · 429 tokens

scenario-player