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 monitor-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/monitor-test-run)<a href="https://agentmods.dev/skills/kobiton/automate/monitor-test-run"><img src="https://agentmods.dev/badge/skills/kobiton/automate/monitor-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.00215 | $0.06276 |
| Opus 5 | $0.00108 | $0.03138 |
| Sonnet 5 | $0.00043 | $0.01255 |
| Haiku 4.5 | $0.00021 | $0.00628 |
Grade A, and why
monitor-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 7d 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.
Overview
Given a testRunId, watch the run and narrate it. The skill:
- Reads
live_remediation_enabledonce viagetOrgSettings, so it can explain deterministically what happens when an execution is blocked. - Runs the bundled
scripts/poll-test-run.jsin the background — it watches the run and emits a line only when an execution's state changes (the model never hand-polls). - Reacts to those emitted lines: surfaces a blocker (with the live-remediation URL) when one appears, stays silent in between.
- On the poller's
DONE, does a post-mortem so a blocker is never mistaken for a pass.
The skill is conversational: its "output" is the messages it posts to the user (events + final
summary), not a value returned to a caller. It changes nothing server-side except, optionally,
terminateTestRun if the user asks to stop the underlying run.
Tool naming. This doc refers to Kobiton MCP tools by their bare names (
getOrgSettings,terminateTestRun). The registered name depends on how the host loaded the MCP server (Claude Code as a plugin exposesmcp__plugin_automate_kobiton__getOrgSettings; a repo-local.mcp.jsonexposesmcp__kobiton__getOrgSettings; other hosts differ). Use the bare name and let the host resolve the prefix. (Run state is read by the bundled poller over REST, not via the MCPgetTestRuntool — a background process can't call MCP tools.)
Prerequisites
Runs on any OS, but needs a local filesystem, Node.js 18+, and ~/.kobiton/.credentials — the watch
is a bundled Node poller that reads that file. Where you can't run a local command at all, tell the user
to follow the run in the portal instead. A streamed-output affordance is strongly preferred but not
required: Claude Code uses the Monitor tool, other hosts substitute their own streamed shell / watch /
loop, and a host with none falls back to the foreground loop in Step 2 — see that per-host table,
including what NOT to use (a silent detached process misses the blocker window). See the Skill
compatibility matrix in CLAUDE.md.
What ships with it
2 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.
- 7d ago First seen · 362 lines · 215 tokens per session scan A 97549641fe28
monitor-test-run is a skill published in the GitHub repository kobiton/automate (12 stars, last pushed 3d ago), licensed MIT. It adds 215 tokens to every session and 6,276 once invoked, about $0.0011 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…