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/create-test-runnpx skills add kobiton/automate --skill create-test-rungit 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/create-test-run)<a href="https://agentmods.dev/skills/kobiton/automate/create-test-run"><img src="https://agentmods.dev/badge/skills/kobiton/automate/create-test-run.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.1 | $0.00207 | $0.02973 |
| Opus 5 | $0.00103 | $0.01486 |
| Sonnet 5 | $0.00041 | $0.00595 |
| Haiku 4.5 | $0.00021 | $0.00297 |
Grade A, and why
create-test-run 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prerequisites
Needs only an authenticated Kobiton MCP connection — no local filesystem, no credentials file, no
binary, no shell. It is the plugin's only pure-MCP skill, so it is the only one that works where the
host supplies nothing else. The monitoring hand-off in Step 5 is the exception: monitor-test-run
runs a local poller, so where you can't run a local command at all, create the run and report its id
instead of offering to watch it (Step 5 carries the wording). Where you can, hand off and let that
skill check its own credentials and streaming options — it degrades rather than refusing. See the Skill
compatibility matrix in CLAUDE.md.
Overview
Turn a "run this" request into a created test run with as little friction as the user wants, then offer to watch it. Two phases:
- Build + confirm the run. Resolve what to run (test case or suite), on which devices, with what app — filling any unspecified field with a documented default — then show a one-screen summary and create on confirmation.
- Offer monitoring once. After creation, present the monitor choice in a
single prompt and delegate to
monitor-test-runif the user wants it.
Tool naming. Kobiton MCP tools are referenced by bare name (
createTestRun,getOrgSettings,listDevices,getTestCase,getTestSuite). The host resolves the prefix (mcp__plugin_automate_kobiton__createTestRun,mcp__kobiton__createTestRun, etc.).
Inputs
| Input | Required | Notes |
|---|---|---|
| test case id or test suite id | one of | A test case id → TEST_CASE selection; a suite id → TEST_SUITE. If the user named neither, ask for it (it's the one thing with no sensible default). |
| device count / specific devices | no | Default: 1 device matching the test case/suite platform. The user may say "3 devices", name models, or give UDIDs. |
| run name / app version / allocation | no | All defaulted (see Step 2). |
Steps
1. Resolve the target and its platform
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 · 208 lines · 207 tokens per session scan A 1f7f858f1e0d
create-test-run is a skill published in the GitHub repository kobiton/automate (12 stars, last pushed 2d ago), licensed MIT. It adds 207 tokens to every session and 2,973 once invoked, about $0.0010 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
swift_expert
Swift and iOS/macOS specialist. Protocol-oriented programming and SwiftUI patterns.
app-ui-design
Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.
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.
harmonyos-development
Use when developing, reviewing, debugging, or migrating HarmonyOS NEXT native apps with ArkTS, ArkUI, DevEco Studio, DevEco Code, DevEco CLI, Agent Framework Kit, Stage model, UIAbility, .ets, module.json5, oh-package.json5, HAP/HSP/HAR, API 22-24, API 26 Beta1, HarmonyOS 6.1, HarmonyOS 6.1.1 Release, HarmonyOS 7…
lov-mobile-adapt
Adapt an existing web project for mobile devices: fix overflow, add responsive layouts, convert to multi-level page navigation with back support, handle notch/Dynamic Island safe areas, fix 100vh browser chrome issues, and optimize touch targets. Trigger when user says "mobile adapt", "移动端适配", "responsive…