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 ofcskn/mobile-automation-plugin --skill optimizing-aso-seogit clone --depth 1 https://github.com/ofcskn/mobile-automation-pluginWrote 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/ofcskn/mobile-automation-plugin/optimizing-aso-seo)<a href="https://agentmods.dev/skills/ofcskn/mobile-automation-plugin/optimizing-aso-seo"><img src="https://agentmods.dev/badge/skills/ofcskn/mobile-automation-plugin/optimizing-aso-seo.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.1 | $0.00099 | $0.00615 |
| Opus 5 | $0.00049 | $0.00308 |
| Sonnet 5 | $0.00020 | $0.00123 |
| Haiku 4.5 | $0.00010 | $0.00061 |
Grade A, and why
optimizing-aso-seo 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 7d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimizing ASO/SEO
When to use
| Request | Action |
|---|---|
| "optimize keywords" | Run ASO optimizer lens for each locale |
| "keyword research" | Load aso-optimizer.lens.md, fill parameters |
| "write store description" | Use lens output, validate character counts |
| "competitor analysis" | Lens includes competitor gap analysis |
| "align screenshots with keywords" | Cross-reference keywords.txt with screenshot-designer.lens.md output |
Core ASO rules
iOS search surface (160 chars total)
- App Name (30) + Subtitle (30) + Keywords (100) = all indexed characters
- Description: 4,000 chars — NOT indexed — conversion copy only
- Do not repeat words across fields (Apple auto-indexes cross-field)
- Single words > phrases in keywords field
- No spaces after commas in keywords:
habit,streak,dailyNOThabit, streak, daily
Google Play search
- Title (30) + Short Description (80) = most weighted signals
- Full Description (4,000) IS indexed — include keywords 3-5× naturally
- What's New: 500 chars (NOT 4,000) — NOT indexed
Apple OCR screenshot indexing (since June 2025)
- Caption headlines on screenshots ARE indexed
- Align slide 1 headline with top keyword from keywords.txt
- Use
lenses/screenshot-designer.lens.mdto generate keyword-aligned caption brief
Process
- Load
lenses/aso-optimizer.lens.md - Fill parameters: app name, category, description draft, target locale, top 3 competitors
- Review output — especially keyword field (must fit in 100 chars, no spaces after commas)
- Write approved values to
.msd/metadata/{appId}/ios/{locale}/and.msd/metadata/{appId}/android/{locale}/ - Validate:
node skills/managing-store-metadata/scripts/validate-metadata.js {appId} - Repeat for each locale (run lens once per locale)
Locale-specific keyword research
Do not simply translate English keywords — research native-language search terms. Example: Turkish users search "alışkanlık takip" not "habit tracker". The aso-optimizer lens handles this automatically when given the target locale.
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.
- 7d ago First seen · 57 lines · 99 tokens per session scan A 5f43d348309b
optimizing-aso-seo is a skill published in the GitHub repository ofcskn/mobile-automation-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 99 tokens to every session and 615 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.
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.
app-store-preflight-compliance
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.
greenlight
It now lives at skills/greenlight/SKILL.md.
e2e-testing
AI-powered E2E testing for any app — Flutter, React Native, iOS, Android, Electron, Tauri, KMP, .NET MAUI. Connects via MCP to running apps so the agent can take screenshots, tap elements, enter text, scroll, inspect UI trees, and verify state with natural language. Use when the user wants to test an app's UI…
browser-tools
Security wrapper over the upstream agent-browser skill, adding URL blocklisting, rate limiting, robots.txt enforcement, and scraping guardrails. Use when automating browser workflows that need safety limits.