Argent is a toolkit that lets an AI assistant control and inspect iOS, Android, TV, Electron, and Chromium applications through simulators, emulators, physical devices, or desktop connections. It is for developers who want an agent to interact with interfaces, reproduce issues, test features, debug applications, or run profiling tasks. The catalogue add-ons expose Argent's device-control and development workflows to coding agents.
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 software-mansion/argent --skill argent-qa-e2egit clone --depth 1 https://github.com/software-mansion/argentWrote 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/software-mansion/argent/argent-qa-e2e)<a href="https://agentmods.dev/skills/software-mansion/argent/argent-qa-e2e"><img src="https://agentmods.dev/badge/skills/software-mansion/argent/argent-qa-e2e/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/software-mansion/argent/argent-qa-e2e"><img src="https://agentmods.dev/badge/skills/software-mansion/argent/argent-qa-e2e.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.00137 | $0.02806 |
| Opus 5.5 | $0.00055 | $0.01122 |
| Sonnet 5.5 | $0.00027 | $0.00561 |
| Haiku 4.5 | $0.00014 | $0.00281 |
Grade A, and why
argent-qa-e2e 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 today.
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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a QA regression e2e test
Load argent-create-e2e as the authoring engine. Follow its required references for recorder syntax, selectors, polish, platform exceptions, and repair. This skill adds the QA contract and completion gate.
Vega supports every item below: launch: { vega: ... }, await:/assert: selectors, snapshot:, and idle all run there. Only the touch directives are missing, because Vega is remote-driven. Navigate with recorded tool: tv-remote steps and type with tool: keyboard, which leaves item 5 with nothing to govern. A D-pad path is relative to where focus already is, so gate every move with item 4's identity check rather than assuming the cursor landed. Read argent-tv-interact for focus reading and remote navigation.
Apple TV and Android TV are out of scope. The runner does not reject touch directives there, so they fail at the gesture layer instead of with authoring guidance. Use argent-tv-interact and report the limitation.
Physical iPhones run QA e2e tests, with three hardware limits: replay never auto-binds a phone, so pass its udid as device (CLI --device) and keep it connected; pinch/rotate steps fail there like the live tools, so drive the app's own zoom UI instead; the runner tree is the describe tree (same ids and roles), so a selector authored on a simulator can miss there. Read argent-ios-device-interact for the app-scoped contract before recording.
Definition of done
A QA e2e test is complete only when:
- The first step that is not
echo:orscript:islaunch:. In-test setup proves a deterministic data baseline. Repeated runs do not accumulate artifacts or require manual cleanup. - The first walkthrough recorded every action and live structural check. Only the three documented polish insertions are unrecorded.
- Every requirement maps to a hard
await:,assert:, or reviewedsnapshot:. Echoes and screenshots are not verdicts. A negative check needs the same stable selector established as visible earlier. - Every screen change has destination identity followed by
idlereadiness. - Targets satisfy the stable-selector and coordinate-fallback rules. QA keeps coordinates only for genuinely unlabeled targets. Vacuous on Vega, which has no coordinate targets.
- The unchanged YAML passes twice with the same runner. Pass 1 starts with fresh mobile Argent services, and pass 2 follows immediately.
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.
- today First seen · 131 lines · 137 tokens per session scan A 013c2ecee434
argent-qa-e2e is a skill published in the GitHub repository software-mansion/argent (3,064 stars, last pushed yesterday), licensed Apache-2.0. It adds 137 tokens to every session and 2,806 once invoked, about $0.0005 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-21.
Other skills, from other repositories
Detox Mobile Testing
Gray-box end-to-end testing for React Native apps with Detox. Covers .detoxrc.js configuration, build and test commands, matchers, device.launchApp control, automatic synchronization, and macOS CI pipelines.
maestro-mobile-testing
Maestro mobile E2E testing patterns for React Native/Expo apps: YAML test flows, testID selectors, adaptive auth state, optimistic update verification, GraalJS scripting, cross-platform stability, CI/CD integration, Maestro Cloud, and MCP server integration.
mobile-automation
Control Android and iOS devices, emulators and simulators — launch apps, tap, swipe, type, take screenshots, read the accessibility tree. Use when a task involves a mobile device or app, mobile UI testing, or reproducing a bug on a phone.
mobilewright-cli
Automate iOS and Android apps on simulators, emulators and real devices, explore screens and write Mobilewright tests.
Appium Mobile Testing
Mobile application testing skill using Appium for iOS and Android, covering device capabilities, selectors, gestures, and cross-platform testing strategies.
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.