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 applyra-io/mcp-server --skill aso-researchgit clone --depth 1 https://github.com/applyra-io/mcp-serverWrote 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/applyra-io/mcp-server/aso-research)<a href="https://agentmods.dev/skills/applyra-io/mcp-server/aso-research"><img src="https://agentmods.dev/badge/skills/applyra-io/mcp-server/aso-research/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/applyra-io/mcp-server/aso-research"><img src="https://agentmods.dev/badge/skills/applyra-io/mcp-server/aso-research.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.00119 | $0.01456 |
| Opus 5.5 | $0.00048 | $0.00582 |
| Sonnet 5.5 | $0.00024 | $0.00291 |
| Haiku 4.5 | $0.00012 | $0.00146 |
Grade A, and why
aso-research 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 9d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASO research with Applyra
Applyra tracks the user's apps on the App Store and Google Play every day. Its tools read that data, and score listing text on the same engine that audits live listings. No tool publishes anything to App Store Connect or Google Play: the user ships changes themselves.
Ground rules
- Start from
list_applications. It gives each app's numericid, which every app-scoped tool takes, with its store, country and language. Never guess an ID.add_applicationandadd_competitorare the exceptions: they take the store bundle ID. - Every number comes from a tool call. Say which tool it came from, with the store, the country and the date of the data. Quote difficulty and traffic as the 0-100 scores Applyra returns.
- Rankings are per store and per country. Keep markets apart, never blend them into one figure.
- Let
check_metadatacount lengths. The stores count UTF-16 code units, not characters, so a count done by hand is wrong in many languages. - Ask before changing the account.
track_keywords,untrack_keyword,set_keyword_favorite,add_application,add_competitorandremove_competitorchange what Applyra tracks, andadd_note,update_noteanddelete_notechange the notes on its charts. Every other tool only reads. - Reuse past work first.
list_keyword_inspections,list_niche_analyses,list_metadata_simulationsandlist_autocomplete_historyreturn what was already run.
What moved
list_keywordsfor the app: current rank, the apps just ahead and behind, the top 5.get_keyword_rank_historyon the keywords that moved, with thekeyword_idfromlist_keywords. It covers the last 30 days unless a range is given.- Report before and after, largest drops first. A move of one or two places is daily noise: lead with the large ones.
- When many keywords fell on the same day,
get_app_score_historyshows whether the app's overall visibility fell with them. A drop across the board on one date usually comes from the store, not from the listing: itsevents.store_updateslist the store algorithm updates of the market.
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.
- 9d ago Changed · +11 lines 5361344babe8
- 14d ago Changed · +60 lines · +68 tokens per session 285f35925ad9
- 22d ago First seen · 24 lines · 51 tokens per session scan A 7e923d6d414c
aso-research is a skill published in the GitHub repository applyra-io/mcp-server (0 stars, last pushed 10d ago), licensed MIT. It adds 119 tokens to every session and 1,456 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-09-30.
Other skills, from other repositories
aso-playbook
Beginner-friendly App Store Optimization guide covering keyword research, screenshot design, rating management, and A/B testing for iOS and Android. By @WeiYipei — practical ASO for indie developers and small teams.
gingiris-aso-growth
A broad guide to growing mobile apps through App Store Optimization, launch planning, creator-made content, and marketing on platforms such as TikTok, Instagram, and YouTube Shorts.
gr-aso
A skill for app-store optimization, or improving how an app is found and presented in the App Store and Google Play, plus launch planning for a new app. It covers listing text, screenshots and video, ratings, creator content, advertising, and localization.
appshot-core
Foundation skill for Appshot. Defines the Remotion project architecture, primitives library, config schema, device presets, and store requirements. Owns the shared extraction phase used by appshot-videos and appshot-images.
appshot-images
Generate App Store and Google Play screenshot designs. Use when the user wants to create store listing images, screenshot mockups, or promotional graphics for a mobile app. Builds on appshot-core foundation.
appshot-videos
Generate App Store / Google Play preview videos using Remotion. Scans the target app's codebase, proposes custom scenes, and writes bespoke .tsx scene files using shared animation primitives. Mobile apps only (iOS/Android). Use when the user wants to create a demo video, app preview, promo video, or marketing video…