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 skills add kobiton/automate --skill drive-automation-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/drive-automation-session)<a href="https://agentmods.dev/skills/kobiton/automate/drive-automation-session"><img src="https://agentmods.dev/badge/skills/kobiton/automate/drive-automation-session/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.
<a href="https://agentmods.dev/skills/kobiton/automate/drive-automation-session"><img src="https://agentmods.dev/badge/skills/kobiton/automate/drive-automation-session.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 173 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 328 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Excessive Agency · line 101 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00150 | $0.06227 |
| Opus 5.5 | $0.00060 | $0.02491 |
| Sonnet 5.5 | $0.00030 | $0.01245 |
| Haiku 4.5 | $0.00015 | $0.00623 |
Grade A, and why
drive-automation-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 11d 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drive from Intent
Overview
Drive a Kobiton device from a natural-language intent. The caller provides:
- An intent string (e.g. "open Settings, enable Bluetooth, then go back to home").
- A UDID for a device the caller has already reserved.
- An app reference (
kobiton-store:vXXXXX) or a browser name for web sessions.
The skill opens an automation-type Appium session (with appium:newCommandTimeout: 1800 so the session survives pauses while the model asks for guidance), runs an observe-decide-act loop, and returns the session id. The returned session is consumable by the Kobiton MCP tools getSession, getSessionArtifacts, and saveTestCase exactly like any other automation session.
Tool naming. This doc refers to Kobiton MCP tools by their bare names (
getSession,reserveDevice,terminateSession, …). The exact registered name depends on how the host loaded the MCP server (e.g. Claude Code as a plugin exposesmcp__plugin_automate_kobiton__getSession; a repo-local.mcp.jsonorclaude mcp addexposesmcp__kobiton__getSession; other hosts differ). Models fuzzy-match on the bare name, so use it and let the host resolve the prefix.
userIntent. Optional: pass one sentence on why when the tool name and arguments show what the call does but not why (e.g.terminateSession,deleteTestCase); omit it when the reason is obvious from the call (e.g.listDevices,getSession).
This skill complements — and does NOT replace — run-interactive-session. They serve different session types:
| Skill | Session type | Best for |
|---|---|---|
run-interactive-session |
CLI session (~/.kobiton/bin/kobiton) |
Human-driven exploration, ad-hoc inspection |
drive-automation-session |
Automation session (direct Appium HTTP) | AI-driven flows, saveable as a test case |
Prerequisites
Runs on any OS, but needs two things from the host: a persistent local filesystem — the observe-decide-act loop passes state between turns through the timestamped artifact files under .kobiton/sessions/<session-id>/, so that file handoff is the loop — and ~/.kobiton/.credentials, which scripts/appium.js reads directly (see below). A host with a filesystem but no way to run /automate:setup still can't finish; route those users to create-test-run. Node.js 18+; no native binary (scripts/appium.js uses node:https). See the Skill compatibility matrix in CLAUDE.md.
What ships with it
13 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.
- references/capabilities.md 4.5 KB
- references/endpoint-reference.md 10 KB
- references/loop-discipline.md 17 KB
- references/webdriver.md 22 KB
- scripts/__fixtures__/uiautomator2-settings.xml 43 KB
- scripts/__fixtures__/webview-mobile-sample.xml 50 KB
- scripts/__fixtures__/xcuitest-settings.xml 29 KB
- scripts/appium.js 21 KB runs code
- scripts/appium.test.js 43 KB runs code
- scripts/strip-webview-dom.js 2.7 KB runs code
- scripts/strip-webview-dom.test.js 4.9 KB runs code
- scripts/ui-tree.js 8.0 KB runs code
- scripts/ui-tree.test.js 12 KB runs code
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.
- 11d ago Changed · +2 lines 848fb28212e7
- 15d ago Changed · -7 lines 6c5bd3faeea3
- 1mo ago First seen · 367 lines · 150 tokens per session scan A 9efc4959264a
drive-automation-session is a skill published in the GitHub repository kobiton/automate (14 stars, last pushed 12d ago), licensed MIT. It adds 150 tokens to every session and 6,227 once invoked, about $0.0006 per session on Opus 5.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.
mobiloop-mobile-qa
Test mobile apps with MobiLoop MCP, collect device evidence, and fix and retest confirmed failures within the user's scope. Use for Flutter, React Native, Android, or iOS QA on an emulator, simulator, or device, including relevant mobile security checks.
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…