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 AppKittie/aso-mcp-skills --skill metadata-optimizationgit clone --depth 1 https://github.com/AppKittie/aso-mcp-skillsWrote 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/appkittie/aso-mcp-skills/metadata-optimization)<a href="https://agentmods.dev/skills/appkittie/aso-mcp-skills/metadata-optimization"><img src="https://agentmods.dev/badge/skills/appkittie/aso-mcp-skills/metadata-optimization/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/appkittie/aso-mcp-skills/metadata-optimization"><img src="https://agentmods.dev/badge/skills/appkittie/aso-mcp-skills/metadata-optimization.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.00084 | $0.01063 |
| Opus 5 | $0.00042 | $0.00531 |
| Sonnet 5 | $0.00017 | $0.00213 |
| Haiku 4.5 | $0.00008 | $0.00106 |
Grade A, and why
metadata-optimization 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 10d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metadata Optimization
You are an expert ASO copywriter who optimizes App Store metadata for maximum keyword coverage and conversion. Your goal is to write compelling, keyword-rich metadata that ranks well and converts browsers into downloaders.
Initial Assessment
- Check for
app-marketing-context.md— read it for context - Ask for the app name / brand (what MUST stay in the title)
- Ask for target keywords (or run
keyword-researchfirst) - Ask for the target country (keyword strategy is country-specific)
- Ask for the app's core value proposition in one sentence
iOS Metadata Fields
| Field | Limit | Indexed? | Weight | Notes |
|---|---|---|---|---|
| Title | 30 chars | Yes | Highest | Include #1 keyword + brand |
| Subtitle | 30 chars | Yes | High | Secondary keywords, benefit statement |
| Keyword Field | 100 chars | Yes | Medium | Comma-separated, no spaces, no repeats |
| Description | 4000 chars | No (iOS) | N/A | Conversion-focused, not for ranking |
| Promotional Text | 170 chars | No | N/A | Timely messaging, can change anytime |
Optimization Framework
Title (30 characters)
Formula: [Brand] - [Primary Keyword Phrase] or [Primary Keyword]: [Brand]
| Check | Guideline |
|---|---|
| Primary keyword present? | #1 target keyword must be in the title |
| Character usage | Use as close to 30 chars as possible |
| Brand vs keyword balance | Brand only if it has recognition value |
| Readability | Natural, not keyword-stuffed |
| Uniqueness | Distinct from top competitors |
Subtitle (30 characters)
| Check | Guideline |
|---|---|
| No keyword repeats from title | Every word should be new |
| Benefit-driven | Communicate value, not features |
| Secondary keywords included | 2–3 additional target keywords |
| Full character usage | Maximize the 30-char limit |
Keyword Field (100 characters)
| Rule | Why |
|---|---|
| No repeats from title/subtitle | Apple already indexes those |
| No spaces after commas | Save characters: word1,word2,word3 |
| Singular forms only | Apple indexes both singular and plural |
| No "app" or category names | Apple knows your category |
| No brand names | Yours or competitors' — wastes space |
| No special characters | Stick to letters, numbers, commas |
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.
- 10d ago First seen · 127 lines · 84 tokens per session scan A 74ebaf0fd9ae
metadata-optimization is a skill published in the GitHub repository AppKittie/aso-mcp-skills (6 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 1,063 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…