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 vishalvshekkar/app-store-toolkit --skill competitorsgit clone --depth 1 https://github.com/vishalvshekkar/app-store-toolkitWrote 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/vishalvshekkar/app-store-toolkit/competitors)<a href="https://agentmods.dev/skills/vishalvshekkar/app-store-toolkit/competitors"><img src="https://agentmods.dev/badge/skills/vishalvshekkar/app-store-toolkit/competitors.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.00017 | $0.00756 |
| Opus 5 | $0.00009 | $0.00378 |
| Sonnet 5 | $0.00003 | $0.00151 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
app-store-toolkit:competitors 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 8d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/app-store-toolkit:competitors
You are analyzing competitor App Store listings to provide ASO insights.
Steps
1. Understand the Request
Parse $ARGUMENTS to determine what competitors to analyze. The user might provide:
- A search term (e.g., "productivity timer")
- A specific app name (e.g., "Forest")
- A category (e.g., "Productivity")
1b. Load Current Metadata (Optional)
Call store_read_config and store_read_metadata to load the user's existing metadata for comparison.
If no config exists, that's OK — competitor analysis can still run without local metadata, but keyword gap analysis will be skipped.
2. Research Competitors
Use web search to find competitor App Store listings. Search for:
site:apps.apple.com "{query}"to find specific apps"{query}" app store top appsfor category research- Look at Apple's App Store search results for the query
For each competitor (analyze 3-5 top competitors):
- App name and subtitle
- Key features highlighted in description
- Keywords used (inferred from name, subtitle, description)
- Rating and review count
- Category and ranking position
3. Keyword Gap Analysis
Compare competitors' keyword strategies with the user's current metadata:
- Read user's current metadata via
store_read_configandstore_read_metadata - Identify keywords competitors use that the user doesn't
- Identify unique keywords the user has that competitors don't
- Suggest high-value keywords to add
4. Present Analysis
Competitor Analysis: "productivity timer"
═══════════════════════════════════════════════════
1. Forest — Stay Focused (4.8 stars, 500K+ ratings)
Name Strategy: Brand + clear benefit
Keywords observed: focus, study, timer, productivity, pomodoro
Strength: Strong emotional branding, gamification angle
2. Focus Timer — Pomodoro (4.6 stars, 100K+ ratings)
Name Strategy: Feature-first + technique name
Keywords observed: pomodoro, focus, timer, study, concentration
Strength: Direct keyword match in name
3. Be Focused — Focus Timer (4.5 stars, 50K+ ratings)
Name Strategy: Action verb + feature
Keywords observed: focus, timer, productivity, work, break
Strength: Action-oriented naming
Keyword Gaps (terms competitors use that you don't):
- pomodoro (3/3 competitors)
- study (2/3 competitors)
- concentration (2/3 competitors)
Your Unique Keywords:
- organize, planning, goals
Recommendations:
1. Add "pomodoro" to keywords — high search volume, all competitors use it
2. Consider "study" — captures student demographic
3. Your name could benefit from a clearer benefit descriptor
═══════════════════════════════════════════════════
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.
- 8d ago First seen · 96 lines · 17 tokens per session scan A 3af13841adc5
app-store-toolkit:competitors is a skill published in the GitHub repository vishalvshekkar/app-store-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 756 once invoked, about $0.0001 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…