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 peters/horizon --skill horizon-app-testinggit clone --depth 1 https://github.com/peters/horizonWrote 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/peters/horizon/horizon-app-testing)<a href="https://agentmods.dev/skills/peters/horizon/horizon-app-testing"><img src="https://agentmods.dev/badge/skills/peters/horizon/horizon-app-testing/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/peters/horizon/horizon-app-testing"><img src="https://agentmods.dev/badge/skills/peters/horizon/horizon-app-testing.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.00048 | $0.00210 |
| Opus 5.5 | $0.00019 | $0.00084 |
| Sonnet 5.5 | $0.00010 | $0.00042 |
| Haiku 4.5 | $0.00005 | $0.00021 |
Grade A, and why
horizon-app-testing 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 8d 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.
What it actually says
Horizon native app testing
Use the separately configured native MCP server for declared iOS and Android tests. Read the app and companion backend instructions before a device run. Read the native app reference for prerequisites, interactive sessions, evidence, and recovery. Use current MCP schemas for arguments.
Use only the approved native device quota and declared loopback ports.
A browser quota does not authorize native devices. Keep provider credentials in Horizon.
Use one immutable artifact per platform per run and isolated synthetic backends.
Observe interactive tests through a live native Device panel in the current workspace.
Use horizon-device for viewer presentation checks; use app_* for native input.
Do not send native input through a browser or through a viewer's Interact toggle.
What ships with it
1 file 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.
- 8d ago First seen · 19 lines · 48 tokens per session scan A 815473721457
horizon-app-testing is a skill published in the GitHub repository peters/horizon (717 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 210 once invoked, about $0.0002 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-10-09.
Other skills, from other repositories
appium-python-expert
Specialist skill for mobile E2E testing with Appium 2.x + Python (pytest) for Android and iOS. Use this skill whenever the user asks about: setting up Appium with Python, writing mobile test cases, configuring Android/iOS drivers (UIAutomator2, XCUITest), implementing Page Object Model for mobile, running tests with…
web-test
A browser-testing tool for 1C:Enterprise, an enterprise business software platform, using Playwright to automate the web client.
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.