setup

A setup command for the Kobiton testing service, which provides cloud-hosted mobile devices. It installs the local command-line wrapper and saves credentials retrieved from the authenticated Kobiton connection.

In plain words
What is it for?
Use it after installing the Kobiton add-on, especially when the command-line wrapper is missing or credentials need to be fetched again.
Why use it?
It prepares the local tools and login information needed by Kobiton automation commands, so later device sessions can start correctly.

Command

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 commands/kobiton/automate/setup
Clone the repo
git clone --depth 1 https://github.com/kobiton/automate
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,552 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.

ModelPer sessionOnce invoked
Fable 5 $0.00021 $0.02552
Opus 5 $0.00010 $0.01276
Sonnet 5 $0.00004 $0.00510
Haiku 4.5 $0.00002 $0.00255

Measured 2d ago against content hash 61731b421b36, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup 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 2d 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.

commands/setup.md · 188 lines

How it starts

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

Kobiton Automate Setup

Bootstrap the plugin: ensure the CLI wrapper symlink is installed, then fetch the user's Kobiton credentials via the getCredential MCP tool and write them to ~/.kobiton/.credentials. After writing, recommend running /automate:doctor to verify.

Step 0: Ensure the CLI wrapper is installed

The run-interactive-session skill depends on ~/.kobiton/bin/kobiton. Claude Code and Codex CLI both recreate this wrapper automatically via a bundled SessionStart hook; on Codex, the user trusts the hook once via /hooks after install. This command (/automate:setup) re-installs the wrapper on demand. GitHub Copilot CLI and Gemini CLI also load /automate:setup (Copilot via Claude-format .md, Gemini via the bundled TOML at commands/automate/setup.toml) — neither has a SessionStart hook, so users on those CLIs run /automate:setup once after install. Cursor CLI loads this same .md via the commands field in .cursor-plugin/plugin.json, but registers it without the plugin namespace (it appears as /setup, distinguishable from Cursor's built-in /setup by its Kobiton description) and does not run the SessionStart hook - so Cursor CLI users also run this command once after install.

Run the install script bundled with this plugin. This file (setup.md) lives at <plugin-root>/commands/setup.md, so the install script is at <plugin-root>/scripts/install-cli.sh. Resolve <plugin-root> to its absolute path and run:

bash <plugin-root>/scripts/install-cli.sh

The script is idempotent. On first run it downloads the CLI build pinned by this plugin release from public.kobiton.download (sha256-verified, cached under ~/.kobiton/cli/) — that needs network access once; every later run is a cache hit with no network I/O. It then installs the ~/.kobiton/bin/kobiton entry point (a symlink to the plugin's wrapper on macOS/Linux, a bash exec-shim on Windows). Supported platforms: macOS on Apple Silicon, Linux x64, Windows x64 (Git Bash). After it returns, sanity-check the result:

Read the full file on GitHub · 188 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.

  1. 2d ago First seen · 188 lines · 21 tokens per session scan A 61731b421b36

Subscribe to this mod's changes

setup is a command published in the GitHub repository kobiton/automate (12 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 2,552 once invoked, about $0.0001 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.