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.
/plugin marketplace add xbim08/awesome-claude-code-pluginsnpx agentmods add plugins/xbim08/awesome-claude-code-plugins/app-store-optimizergit clone --depth 1 https://github.com/xbim08/awesome-claude-code-pluginsGrade 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 yesterday.
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.
This is a copy
100% identical to app-store-optimizer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"name": "app-store-optimizer",
"description": "Use this agent when preparing app store listings, researching keywords, optimizing app metadata, improving conversion rates, or analyzing app store performance. This agent specializes in maximizing organic app store visibility and downloads. Examples:\\n\\n<example>\\nContext: Preparing for app launch",
"version": "1.0.0",
"author": {
"name": "Michael Galpert"
},
"homepage": "https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/app-store-optimizer"
}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.
- yesterday First seen · 9 lines scan A 33eaf590977b
app-store-optimizer is a plugin published in the GitHub repository xbim08/awesome-claude-code-plugins (10 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. It is 100% identical to app-store-optimizer, differing in 0 lines, and is treated as a copy.
Other plugins, from other repositories
ai-engineer
Use this agent when implementing AI/ML features, integrating language models, building recommendation systems, or adding intelligent automation to applications. This agent specializes in practical AI implementation for rapid deployment. Examples:\n\n \nContext: Adding AI features to an app\nuser: "We need AI-po.
app-starter
Bootstrap new Next.js, Flutter, and FastAPI apps with current packages, no deprecated APIs, and a consistent house style. Ships skills nextjs-app, flutter-app, and fastapi-app.
api-tester
Use this agent for comprehensive API testing including performance testing, load testing, and contract testing. This agent specializes in ensuring APIs are robust, performant, and meet specifications before deployment. Examples:\n\n \nContext: Testing API performance under load.
adamsreview
Multi-lens code review pipeline: deep review (Claude or Codex), automated fix loop, interactive walkthrough, manual promote, external-finding injection.
agent-decision-record
Structured decision-making for AI coding agents. Creates auditable Agent Decision Records (AgDR) when technical choices are made.
api-authentication
Secure API authentication with JWT, OAuth 2.0, API keys. Use for authentication systems, third-party integrations, service-to-service communication, or encountering token management, security headers, auth flow errors.