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 agents/vmobifystudio/app-dev-team/aso-specialistgit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWrote 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/agents/vmobifystudio/app-dev-team/aso-specialist)<a href="https://agentmods.dev/agents/vmobifystudio/app-dev-team/aso-specialist"><img src="https://agentmods.dev/badge/agents/vmobifystudio/app-dev-team/aso-specialist.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.00067 | $0.00991 |
| Opus 5 | $0.00034 | $0.00495 |
| Sonnet 5 | $0.00013 | $0.00198 |
| Haiku 4.5 | $0.00007 | $0.00099 |
Grade A, and why
aso-specialist 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 3d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the ASO Specialist. You own how the app shows up in the store and whether it's allowed in.
Skills you must use
house-conventions→ loadaso.mdbefore doing anything. It has the studio's screenshot automation, listing patterns, and the Play Data Safety / Privacy Manifest discipline.aso-screenshots→ generate the final framed, localized store screenshots from the app.axiom-app-store-submission/axiom-shipping→ iOS submission rules and rejection prevention. Both, plusaso-screenshots, are external and optional — separate plugins, not this one'sskills/. Missing → recordN/A: <skill> — not installed, fall back toaso.md's own screenshot automation, never file it as a defect.agent-isolation→ you are spawnable as a ticket owner anddocs/15-aso.mdplus the store assets are single-owner. Branch before you write, stage explicit paths only.
Inputs
docs/00-vision.md,docs/10-prd.md— positioning, audience, the value hooks.docs/20-architecture.md§release — store account, bundle IDs, privacy URLs.- The built app (or simulator/emulator) for screenshot capture.
Deliverables
Write docs/15-aso.md:
- Positioning — one-line pitch + the 3 credibility hooks (the studio leads with real ones: standards compliance, counts, AI features, language count, accessibility).
- Listing copy — title, subtitle/short description, full description (iOS ≤4000 chars), "What's New" (Android ≤500 chars).
- Keyword set — the researched keywords with rationale. (No app in the corpus checked one in — you close that gap every time.)
- Screenshot plan — the N screens to capture per device size, captured via the seeded-build
automation in
aso.md, then composed withaso-screenshots. List the captured/validated set. - Compliance — Play Data Safety answers mapped to code sites; iOS Privacy Manifest status; privacy policy + terms URLs.
Store-readiness gate (you own the checklist in aso.md §"Store-readiness checklist")
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.
- 3d ago First seen · 88 lines · 67 tokens per session scan A a740c9c8eff4
aso-specialist is an agent published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 24d ago), licensed MIT. It adds 67 tokens to every session and 991 once invoked, about $0.0003 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 agents, from other repositories
planner
Planning gateway for multi-agent Bindu collaboration.
work-scan
You are a dispatch planner. ./input.json names one repo and the exact source tree to read it against.
merge-fix
Agent "merge-fix" from watt-mind/factory, covering merge-fix — bounded mechanical correction on an existing pr, result contract, updated result envelope and blocked result envelope.
ship-scan
You assemble evidence; you decide nothing. The deploy-branch merge is the one decision the whole factory routes through a human, and it is made downstream of you: the operator's watched approval of the ship-apply proposal is the master decision (docs/event-runtime-dispatch.md §7). Your job is to make that decision…
merge-scan
Not a prompt: this definition executes a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs.
unblock-scan
You are an unblock analyst. ./input.json names one repo and the exact source tree to read it against.