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 6529-Collections/6529seize-frontend --skill test-mobile-devicesgit clone --depth 1 https://github.com/6529-Collections/6529seize-frontendWrote 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/6529-collections/6529seize-frontend/test-mobile-devices)<a href="https://agentmods.dev/skills/6529-collections/6529seize-frontend/test-mobile-devices"><img src="https://agentmods.dev/badge/skills/6529-collections/6529seize-frontend/test-mobile-devices/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/6529-collections/6529seize-frontend/test-mobile-devices"><img src="https://agentmods.dev/badge/skills/6529-collections/6529seize-frontend/test-mobile-devices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00091 | $0.01687 |
| Opus 5 | $0.00046 | $0.00843 |
| Sonnet 5 | $0.00018 | $0.00337 |
| Haiku 4.5 | $0.00009 | $0.00169 |
Grade A, and why
test-mobile-devices 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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Mobile Devices
Scope
Use this skill to collect and report native mobile evidence for the 6529 frontend. Version 1 covers iOS Simulator and real iPhone flows through the sibling mobile shell repo.
Reserve structure for Android later, but do not run or document Android as supported evidence until a dedicated Android workflow exists.
Push-enabled native testing is explicitly out of scope for this skill. Keep local native workflows no-push unless the user separately asks for a push-enabled production-style mobile setup.
Required Context
- Read the frontend repo
AGENTS.mdand obey the command policy. - Confirm the sibling mobile shell repo is available. Strongly recommend the
local path shape
/Users/<name>/6529-core-mobile. - Confirm the sibling mobile repo is on branch
codex/mobile-dev-workflows. If the repo or branch is unavailable, stop and report blocked. - Read the sibling mobile repo
AGENTS.mdanddocs/mobile-workflows.mdbefore running native shell commands. - Use the frontend repo's documented wrapper for frontend commands. In this
repo, project commands go through
6529.
Do not hardcode a real username, local absolute path, LAN IP, Apple team ID, UDID, bundle ID, or private environment value in reusable instructions, PR text, committed files, or public reports.
Evidence Tiers
Label evidence precisely:
browser-simulation: Playwright projects such ascapacitor-ios-sim,capacitor-android-sim, orelectron-shell-sim. This catches native-branch logic but does not prove a real native shell.package-prerequisites:test:native-evidence:package-prereqsstyle checks. This proves repo/tooling prerequisites, not runtime behavior.simulator-runtime: the iOS native shell launched in Simulator and controlled with simulator UI tools.real-device-runtime: the iOS native shell installed/launched on a physical iPhone and controlled with Appium/XCUITest.
Never claim real-device or packaged-native evidence from browser simulation alone.
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.
- 2d ago Changed · +21 lines 1c1e524b3498
- 12d ago First seen · 163 lines · 91 tokens per session scan A caed3d31ff0e
test-mobile-devices is a skill published in the GitHub repository 6529-Collections/6529seize-frontend (10 stars, last pushed today), licensed Apache-2.0. It adds 91 tokens to every session and 1,687 once invoked, about $0.0005 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-31.
Other skills, from other repositories
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.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
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.
eas-simulator
EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas…
flutter-add-integration-test
Configures Flutter Driver for app interaction and converts MCP actions into permanent integration tests. Use when adding integration testing to a project, exploring UI components via MCP, or automating user flows with the integrationtest package.