Borrowing it
Nothing to install: this file belongs to kobiton/automate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kobiton/automate/main/CLAUDE.mdgit 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/instructions/kobiton/automate/claude-md)<a href="https://agentmods.dev/instructions/kobiton/automate/claude-md"><img src="https://agentmods.dev/badge/instructions/kobiton/automate/claude-md/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/instructions/kobiton/automate/claude-md"><img src="https://agentmods.dev/badge/instructions/kobiton/automate/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.07420 | $0.07420 |
| Opus 5.5 | $0.02968 | $0.02968 |
| Sonnet 5.5 | $0.01484 | $0.01484 |
| Haiku 4.5 | $0.00742 | $0.00742 |
Grade B, and why
automate CLAUDE.md scanned grade B with 1 finding 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 6d 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.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
| Claude Code | `.mcp.json` (OAuth) + `.mcp.apikey-example.json` (API key) | `.claude-plugin/plugin.json` + `.claude-plugin/marketplace.json` | `skills/*/SKILL.md` | How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code when working with code in this repository.
Getting started
The user journey the plugin serves, end to end: /automate:setup → list/reserve a device → drive it (one skill, below) → save the session as a test case (saveTestCase) → optionally create and monitor a test run.
Every skill is a step on that path; route by intent:
| Reach for this when the user wants… | Skill |
|---|---|
| to run local Appium scripts (Node.js/Python/.NET/Java) on Kobiton devices | run-automation-suite |
| a clean hands-off run of a described flow, saveable as a test case | drive-automation-session |
| quick inspection / troubleshooting — poke at a device, pull logs, push files | run-interactive-session |
| to kick off a test run from a test case or suite | create-test-run |
| to watch a running test run and catch blockers | monitor-test-run |
to debug their app on a real device attached to their own machine — see it in adb / Xcode, install a local build, read logcat ("virtualUSB", "vusb", "plug the Kobiton device into my machine") |
debug-device-over-vusb |
Vocabulary the skills assume: session (one recorded device connection), test case (saved replayable steps, usually from a session), test run (execution of a case/suite across devices), test suite (ordered collection of cases), reservation (exclusive device hold), device UDID (unique device identifier), live remediation (browser takeover to fix a blocked execution mid-run).
Ambiguous prompts ("test the login screen of app ABC" — goal named, method not): route by signal — script files mentioned → run-automation-suite; flow described / wants it repeatable → drive-automation-session; diagnostic verbs (explore, poke, logs, adb, push/pull) → run-interactive-session; names an existing case/suite → create-test-run; run already in flight → monitor-test-run.
With no deciding signal, ask ONE question (scripts / agent-driven / hands-on) and recommend drive-automation-session — any platform, plain-language goal, and the session stays saveable via saveTestCase.
Never silently pick run-interactive-session for a "test X" goal: CLI sessions don't feed saveTestCase, so that route forfeits the saveable outcome.
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.
- 6d ago Changed · +79 tokens per session 43791819b9e0
- 10d ago Changed · +1 lines · +167 tokens per session 0497ae7ff806
- 13d ago Changed · +11 lines · +526 tokens per session f41e2a74f3f3
- 17d ago Changed · +63 tokens per session 2d710f9aff9b
- 21d ago Changed · +10 lines · +862 tokens per session 3fc936eea9ee
- 29d ago Changed · +51 tokens per session 652af419095f
- 1mo ago Changed · -2 lines · -113 tokens per session a7dfa7734b6c
- 1mo ago First seen · 211 lines · 5,785 tokens per session scan B 784d02f180ec
automate CLAUDE.md is an instructions file published in the GitHub repository kobiton/automate (14 stars, last pushed 7d ago), licensed MIT. It adds 7,420 tokens to every session, about $0.0297 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.