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 tai2/aco --skill acogit clone --depth 1 https://github.com/tai2/acoWrote 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/tai2/aco/aco)<a href="https://agentmods.dev/skills/tai2/aco/aco"><img src="https://agentmods.dev/badge/skills/tai2/aco/aco/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/tai2/aco/aco"><img src="https://agentmods.dev/badge/skills/tai2/aco/aco.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.00000 | $0.01012 |
| Opus 5.5 | $0.00000 | $0.00405 |
| Sonnet 5.5 | $0.00000 | $0.00202 |
| Haiku 4.5 | $0.00000 | $0.00101 |
Grade A, and why
aco 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 1mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Driving Appium with aco
aco issues one Appium WebDriver command per shell invocation against a live
session. Prerequisite: the user has aco (npm i -g @tai2/aco) and appium
installed. If aco --help fails, stop and tell the user to install it.
Core loop
- Discover a target (only when starting fresh):
aco device list(add--platform ios|android,--state all,--json). - Start a session — foreground blocks the shell, so ALWAYS pass
--detachso control returns:aco session start --detach --platform ios --app <path-or-bundleId> --device-name "<name>"Android needs--app-activitywhen--appis an appPackage id, and--avd(or a plugged-in device) to choose the target.session starthas no--jsonflag — it always emits the JSON envelope on stdout. Do not append--json(it errors); for verbatim W3C caps use--caps-json '<json>'instead. Do NOT unzip the build first. Pass the archive straight to--app: the driver extracts it itself. iOS accepts a.zip/.app.zip/.ipa(or an unzipped.app); Android accepts an.apk/.apks. Unzipping a.app.zipto a bare.appis unnecessary and a common mistake. - Inspect before acting — never guess coordinates:
aco elements→ labelled elements + ready-to-paste tap selectors (use--jsonto parse).aco screenshot --out shot.png, then Readshot.pngto see the screen.aco source(optionally--xpath '<expr>') for the full tree.
- Act —
--session/--server-url/--platformdefault to the latest live session, so omit them aftersession start:aco tap --selector 'accessibility id:login.button'(or--label, or--x/--y).aco swipe --direction up(within the default scroll view).aco send-keys --selector '<sel>' --text 'alice'(clears first;--no-clearappends).aco scroll-into-view '<selector>' --direction up.aco element find --using "accessibility id" --value "Login"thenaco element click --element <id>.
- Verify the effect with another
aco screenshot/aco elements. - Stop when done:
aco session stop(latest),--all, or--session <id>.
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.
- 1mo ago First seen · 72 lines · 0 tokens per session scan A f13d1f1f5c0f
aco is a skill published in the GitHub repository tai2/aco (3 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,012 tokens. 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
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.
mobiloop-mobile-qa
Test mobile apps with MobiLoop MCP, collect device evidence, and fix and retest confirmed failures within the user's scope. Use for Flutter, React Native, Android, or iOS QA on an emulator, simulator, or device, including relevant mobile security checks.
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.
argent-test-ui-flow
Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools. Use when testing UI flows, verifying login works, testing navigation, running end-to-end UI test scenarios, manual QA steps, visible UI changes, or visual behavior.
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.