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 skills/kobiton/automate/run-interactive-sessionnpx skills add kobiton/automate --skill run-interactive-sessiongit clone --depth 1 https://github.com/kobiton/automateWrote 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/kobiton/automate/run-interactive-session)<a href="https://agentmods.dev/skills/kobiton/automate/run-interactive-session"><img src="https://agentmods.dev/badge/skills/kobiton/automate/run-interactive-session.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.00133 | $0.10796 |
| Opus 5 | $0.00067 | $0.05398 |
| Sonnet 5 | $0.00027 | $0.02159 |
| Haiku 4.5 | $0.00013 | $0.01080 |
Grade A, and why
run-interactive-session 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 — 531 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Interactive Test
Overview
Drive a Kobiton device interactively from natural-language intent. Given a request like "find the Login button and tap it" or "pull the latest log file from this Pixel", this skill creates (or resumes) a session, translates the intent into the right CLI command - WebDriver action, adb shell, file transfer, app launch, test run - captures the response, saves artifacts (screenshots, page source) under the workspace, and reports back in plain language.
Use this skill whenever the user wants to interact with a mobile device on Kobiton, run exploratory tests, inspect device state, manage files on a device, or execute test sessions - even if they don't say "interactive test" explicitly.
Prerequisites
Runs on macOS (Apple Silicon), Linux (x64), and Windows (x64 under Git Bash), and needs a local filesystem — it executes a locally cached CLI binary and reads ~/.kobiton/.credentials. On Intel Macs or other unsupported architectures, or anywhere a local filesystem isn't available, don't invoke this skill: route to run-automation-suite (user already has a test script) or drive-automation-session (describe the flow instead), both cross-platform. Check this before reserving a device, so a doomed run doesn't burn device minutes. See the Skill compatibility matrix in CLAUDE.md.
Before invoking this skill, ensure:
- Kobiton CLI wrapper -
~/.kobiton/bin/kobiton(a symlink to this plugin'srun.shwrapper on macOS/Linux, a bash exec-shim on Windows) must exist and resolve to an executable. Claude Code and Codex CLI both recreate it automatically via a bundled SessionStart hook; on Codex, the user trusts the hook once via/hooksafter install./automate:setupre-installs the wrapper on demand on any host. GitHub Copilot CLI and Gemini CLI load/automate:setup(Copilot via Claude-format.md, Gemini via bundled TOML atcommands/automate/setup.toml) but have no SessionStart hook - run/automate:setuponce after install. The CLI binary itself is downloaded, not bundled: the install script fetches the build pinned inCLI_VERSION(sha256-verified) into~/.kobiton/cli/on first run.run.shreports a missing binary or missing credentials with the right remedy, so surface its error rather than pre-flighting your own checks. - Credentials file -
~/.kobiton/.credentialsmust contain a valid INI-formatted profile withKOBITON_USER,KOBITON_API_KEY, andKOBITON_PORTAL. Created by/automate:setup. The active profile is$KOBITON_PROFILEif set, otherwisedefault. - Kobiton MCP connection - useful for
listDevices/getDeviceStatuscalls when picking a device. Defaultapi.kobiton.com/mcp; check.mcp.jsonfor the configured endpoint. - Kobiton account - credentials with device access for the target platform (Android / iOS) and remaining session quota.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 531 lines · 133 tokens per session scan A da1c7ce0f3c3
run-interactive-session is a skill published in the GitHub repository kobiton/automate (12 stars, last pushed 2d ago), licensed MIT. It adds 133 tokens to every session and 10,796 once invoked, about $0.0007 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 skills, from other repositories
Appium Mobile Testing
Mobile application testing skill using Appium for iOS and Android, covering device capabilities, selectors, gestures, and cross-platform testing strategies.
finalrun-use-cli
Use the published FinalRun CLI to install, configure, validate, run, troubleshoot, and inspect reports for repo-local mobile test workspaces. Trigger this skill for requests involving finalrun, check, test, suite, doctor, runs, start-server.
noqa-testing
Use this skill when the user wants to boot and interact with iOS or Android devices/simulators — inspect the screen, execute actions, generate or edit test cases, or run UI tests via the noqa platform.
playwright-for-android
End-to-end Android debug loop on an emulator. Builds the APK with a Gradle task, boots a named AVD, installs and launches the target package, then drives a single feature via adb-injected UI actions while capturing a unified logcat-and-actions timeline plus a developer-facing test report. Use when the user wants to…
mobile-tester
You are the Mobile Tester Specialist. You connect to real Android/iOS devices and write, execute, and report on mobile UI test cases. You master THREE testing modalities.
aco
Drive a live Appium session from the shell with the aco CLI. Use when the user wants to interact with a running mobile app on an iOS simulator, Android emulator, or connected real device — tap, swipe, type, screenshot, read the screen/page source, find UI elements, switch to a WebView context, or call iOS/Android…