Borrowing it
Nothing to install: this file belongs to guiguito/AppStoresMCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/guiguito/AppStoresMCP/main/CLAUDE.mdgit clone --depth 1 https://github.com/guiguito/AppStoresMCPWrote 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/instructions/guiguito/appstoresmcp/claude-md)<a href="https://agentmods.dev/instructions/guiguito/appstoresmcp/claude-md"><img src="https://agentmods.dev/badge/instructions/guiguito/appstoresmcp/claude-md.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.00934 | $0.00934 |
| Opus 5 | $0.00467 | $0.00467 |
| Sonnet 5 | $0.00187 | $0.00187 |
| Haiku 4.5 | $0.00093 | $0.00093 |
Grade A, and why
AppStoresMCP CLAUDE.md 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 6d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Development Commands
Building and Testing
npm run build- Build TypeScript to JavaScriptnpm run test- Run all tests (unit and integration)npm run test:unit- Run unit tests onlynpm run test:integration- Run integration testsnpm run test:coverage- Run tests with coverage reportnpm run lint- Run ESLint
Development
npm run dev- Start development server with ts-nodenpm start- Start production server from dist/
Docker Commands
docker-compose up --build- Build and run with Docker Composenpm run test:integration:docker- Run integration tests in Docker./scripts/generate-ssl-certs.sh- Generate SSL certificates for HTTPS
Architecture Overview
This is a Node.js TypeScript MCP (Model Context Protocol) server that provides app store scraping functionality through multiple transport protocols.
Core Components
MCPServer (src/server.ts) - Main orchestrator that manages:
- HTTP and SSE transport handlers
- Tool registry with 19 MCP tools
- Configuration management
- Graceful shutdown handling
Transport Layer (src/transport/)
- HTTPTransportHandler - MCP Streamable HTTP protocol implementation
- SSETransportHandler - Server-Sent Events transport for legacy MCP clients with automatic initialization
Protocol Handler (src/protocol/mcp-handler.ts)
- Processes MCP messages (initialize, tools/list, tools/call)
- Handles tool execution with error handling and retries
- Returns raw data from underlying scraper libraries
Tool Registry (src/registry/tool-registry.ts)
- Manages 19 MCP tools (10 Google Play, 9 App Store)
- Each tool implements the
MCPToolinterface - Tools are located in
src/tools/directory
Services (src/services/)
- AppStoreScraperService - Wraps app-store-scraper library
- GooglePlayScraperService - Wraps google-play-scraper library
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.
- 6d ago First seen · 113 lines · 934 tokens per session scan A 2b0fed7527df
AppStoresMCP CLAUDE.md is an instructions file published in the GitHub repository guiguito/AppStoresMCP (5 stars, last pushed 7mo ago), licensed MIT. It adds 934 tokens to every session, about $0.0047 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.