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 agentmods add skills/appclawhq/appclaw/use-appclaw-agent-clinpx skills add appclawhq/AppClaw --skill use-appclaw-agent-cligit clone --depth 1 https://github.com/appclawhq/AppClawWrote 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/appclawhq/appclaw/use-appclaw-agent-cli)<a href="https://agentmods.dev/skills/appclawhq/appclaw/use-appclaw-agent-cli"><img src="https://agentmods.dev/badge/skills/appclawhq/appclaw/use-appclaw-agent-cli.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 | $0.00074 | $0.00710 |
| Opus 5 | $0.00037 | $0.00355 |
| Sonnet 5 | $0.00015 | $0.00142 |
| Haiku 4.5 | $0.00007 | $0.00071 |
Grade A, and why
use-appclaw-agent-cli 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 5d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AppClaw Agent CLI
When the user asks you to operate or inspect a mobile device interactively (open an app, tap a button, check visibility, etc.) using terminal commands rather than a YAML flow:
- Verify that
appclaw-agentis installed and runappclaw-agent help workflow. - Use a descriptive named session for the task.
- Inspect with
snapshot -i --jsonbefore choosing a target. - Prefer returned
@eNreferences or durable selectors for interaction. - Request a new snapshot after each state-changing action.
- Use
--visiononly when explicitly requested or when visual targeting is required and configured.
Scrolling — direction reference
Always use scroll, never swipe. scroll and swipe are aliases in the parser, but scroll reads unambiguously — scroll down means scroll down, scroll up means scroll up.
| Goal | Command |
|---|---|
| See content below (scroll down) | appclaw-agent --session <name> scroll down --json |
| See content above (scroll up) | appclaw-agent --session <name> scroll up --json |
| Scroll down within an element | appclaw-agent --session <name> scroll @eN down --json |
| Scroll up within an element | appclaw-agent --session <name> scroll @eN up --json |
Never use swipe — swipe up is ambiguous (training data says it scrolls down; AppClaw treats it as scroll up). Using scroll eliminates the confusion entirely.
Never use swipe @eN direction — element-scoped swipe crashes (swipeElement is not a function). Use scroll @eN direction instead. 7. Close the named session when the task is complete.
Assertions must always be visual
Never use DOM presence (is visible, snapshot element checks) as the sole assertion. The DOM may contain elements that are off-screen, scrolled out of view, or clipped — DOM presence does not mean the user can see it.
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.
- 5d ago First seen · 53 lines · 74 tokens per session scan A 0fe176b9f4cc
use-appclaw-agent-cli is a skill published in the GitHub repository appclawhq/AppClaw (110 stars, last pushed yesterday), licensed Apache-2.0. It adds 74 tokens to every session and 710 once invoked, about $0.0004 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
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.
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.
flutter-cherry-pick
How to land a formal cherry-pick of a merged PR for the flutter/flutter repo stable or beta channel. Only use for flutter/flutter landed pull requests. Only use when the cherry pick request is into "stable", "beta" or a branch that has the format with flutter- . -candidate.0.
updating-android-sdk
Upgrades Flutter's Android SDK dependency to a new Android API version (or preview/canary release) in packages.txt, verifies CIPD tag uniqueness, and packages/uploads the binaries using createcipdpackages.sh across macOS, Linux, and Windows. Use whenever a user wants to pick up a new version of Android or upload…
analyze-github-flake
Expertise in analyzing flake github issues in the flutter/flutter repository. Use when a user wants to analyze the flakiness of a specific link to a flutter github issue.
flutter-pr-checks-finder
Find failing checks on a Flutter PR and locate the corresponding LUCI log URLs.