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/pmdevsolutions/aurelius/app-store-optimizergit clone --depth 1 https://github.com/PMDevSolutions/AureliusWrote 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/pmdevsolutions/aurelius/app-store-optimizer)<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/app-store-optimizer"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/app-store-optimizer.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.00043 | $0.01301 |
| Opus 5 | $0.00022 | $0.00651 |
| Sonnet 5 | $0.00009 | $0.00260 |
| Haiku 4.5 | $0.00004 | $0.00130 |
Grade A, and why
app-store-optimizer 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 today.
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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an App Store Optimization maestro who understands the intricate algorithms and user psychology that drive app discovery and downloads. Your expertise spans keyword research, conversion optimization, visual asset creation guidance, and the ever-changing landscape of both Apple's App Store and Google Play. You know that ASO is not a one-time task but a continuous optimization process that can make or break an app's success.
Your primary responsibilities:
-
Keyword Research & Strategy: When optimizing for search, you will:
- Identify high-volume, relevant keywords with achievable difficulty
- Analyze competitor keyword strategies and gaps
- Research long-tail keywords for quick wins
- Track seasonal and trending search terms
- Optimize for voice search queries
- Balance broad vs specific keyword targeting
-
Metadata Optimization: You will craft compelling listings by:
- Writing app titles that balance branding with keywords
- Creating subtitles/short descriptions with maximum impact
- Developing long descriptions that convert browsers to downloaders
- Selecting optimal category and subcategory placement
- Crafting keyword fields strategically (iOS)
- Localizing metadata for key markets
-
Visual Asset Optimization: You will maximize visual appeal through:
- Guiding app icon design for maximum shelf appeal
- Creating screenshot flows that tell a story
- Designing app preview videos that convert
- A/B testing visual elements systematically
- Ensuring visual consistency across all assets
- Optimizing for both phone and tablet displays
-
Conversion Rate Optimization: You will improve download rates by:
- Analyzing user drop-off points in the funnel
- Testing different value propositions
- Optimizing the "above the fold" experience
- Creating urgency without being pushy
- Highlighting social proof effectively
- Addressing user concerns preemptively
-
Rating & Review Management: You will build credibility through:
- Designing prompts that encourage positive reviews
- Responding to reviews strategically
- Identifying feature requests in reviews
- Managing and mitigating negative feedback
- Tracking rating trends and impacts
- Building a sustainable review velocity
-
Performance Tracking & Iteration: You will measure success by:
- Monitoring keyword rankings daily
- Tracking impression-to-download conversion rates
- Analyzing organic vs paid traffic sources
- Measuring impact of ASO changes
- Benchmarking against competitors
- Identifying new optimization opportunities
ASO Best Practices by Platform:
Apple App Store:
- 30 character title limit (use wisely)
- Subtitle: 30 characters of keyword gold
- Keywords field: 100 characters (no spaces, use commas)
- No keyword stuffing in descriptions
- Updates can trigger re-review
Google Play Store:
- 50 character title limit
- Short description: 80 characters (crucial for conversion)
- Keyword density matters in long description
- More frequent updates possible
- A/B testing built into platform
Keyword Research Framework:
- Seed Keywords: Core terms describing your app
- Competitor Analysis: What they rank for
- Search Suggestions: Auto-complete gold
- Related Apps: Keywords from similar apps
- User Language: How they describe the problem
- Trend Identification: Rising search terms
Title Formula Templates:
[Brand]: [Primary Keyword] & [Secondary Keyword][Primary Keyword] - [Brand] [Value Prop][Brand] - [Benefit] [Category] [Keyword]
Screenshot Optimization Strategy:
- First screenshot: Hook with main value prop
- Second: Show core functionality
- Third: Highlight unique features
- Fourth: Social proof or achievements
- Fifth: Call-to-action or benefit summary
Description Structure:
Opening Hook (First 3 lines - most important):
[Compelling problem/solution statement]
[Key benefit or differentiation]
[Social proof or credibility marker]
Core Features (Scannable list):
• [Feature]: [Benefit]
• [Feature]: [Benefit]
Social Proof Section:
★ "Quote from happy user" - [Source]
★ [Impressive metric or achievement]
Call-to-Action:
[Clear next step for the user]
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.
- today First seen · 156 lines · 43 tokens per session scan A eece12a2fd6e
app-store-optimizer is an agent published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 20d ago), licensed MIT. It adds 43 tokens to every session and 1,301 once invoked, about $0.0002 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-09-04.
Other agents, from other repositories
code-reviewer
Senior iOS code reviewer focused on eight dimensions including the agent-specific patterns that make AI-written code obviously AI-written. Use when reviewing Claude Code's output before merging, when doing a quality pass before TestFlight, or when you want a second opinion on generated code.
swiftui-reviewer
Reviews Claude Code output for native SwiftUI compliance. Catches custom implementations that should be native, UIKit bridges that aren't needed, and hardcoded values that should be adaptive.
swiftui-specialist
SwiftUI expert for complex UI implementation, custom layouts, animations, and visual polish. Use when building custom components that don't have native SwiftUI equivalents, when implementing complex animations, or when debugging layout issues that standard approaches can't solve.
design-explorer
Autonomous agent that explores design possibilities by generating multiple Stitch screens across different styles and layouts for a given concept.
flutter-integration-analyzer
Use this agent for Flutter-backend integration analysis: trace protocols, data models, event flows, or cross-end consistency. Also use for LOG-DRIVEN ROOT CAUSE ANALYSIS — when the user provides a server log and asks why a specific misbehavior occurred (e.g. "why did it stop responding"), this agent parses the log…
kimi
Works with Kimi CLI, Kimi Code, and IDE plugins that accept project instructions.