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 instructions/laurmost/appstore-mcp/agents-mdgit clone --depth 1 https://github.com/LaurMost/appstore-mcpWrote 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/laurmost/appstore-mcp/agents-md)<a href="https://agentmods.dev/instructions/laurmost/appstore-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/laurmost/appstore-mcp/agents-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 | $0.00885 | $0.00885 |
| Opus 5 | $0.00443 | $0.00443 |
| Sonnet 5 | $0.00177 | $0.00177 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
appstore-mcp AGENTS.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 3d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
appstore-mcp
Open-source MCP server for live Apple App Store competitor research.
Python 3.12, uv, fastmcp. Design record: CONTEXT.md (domain glossary) +
docs/adr/ (decisions) — see docs/agents/domain.md. There is no PLAN.md;
the original v1 design doc was fully redistributed into ADRs, CONTEXT.md,
and this file once the decisions it recorded had settled.
Depend on the fastmcp package (jlowin's actively-developed one) — not the
frozen FastMCP bundled in the official mcp SDK. mcp[cli] is not a
dependency; don't reintroduce it.
Local dev server: fastmcp dev (Inspector UI, stdio) or fastmcp run
(standalone), driven by fastmcp.json — see README's Development section.
Tool surface
7 read-only MCP tools over public Apple App Store data (search_app_store,
get_app_store_app, compare_app_store_apps, get_app_store_charts,
get_app_store_reviews, digest_app_store_reviews,
get_app_store_screenshots), plus one prompt, compare_competitors. Tool
orchestration lives in src/appstore_mcp/tools/ (one module per tool),
server.py stays thin registrations, and apple/ stays single-source API
clients per upstream domain — see
docs/adr/0002-tools-package-for-orchestration.md for why. This list will
drift as tools are added; server.py's @mcp.tool decorators are the
source of truth for exact signatures, not this file.
Conventions for any new tool:
readOnlyHint: true,idempotentHint: true,openWorldHint: trueannotations; an explicittimeout; numeric limits asAnnotated[int, Field(ge=..., le=...)], never manual clamping; a Google-styleArgs:docstring section so FastMCP generates per-parameter schema descriptions.- Compact, normalized response by default — raw upstream payloads are
opt-in only (
docs/adr/0004-compact-response-shape-with-raw-opt-in.md). - Failures follow the two-tier split in
docs/adr/0006-two-tier-failure-semantics.md: a broken promise raises; in-band degradation returns success plusmeta.warnings/per-itemerrors.
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.
- 3d ago First seen · 76 lines · 885 tokens per session scan A 2a4b215a9c21
appstore-mcp AGENTS.md is an instructions file published in the GitHub repository LaurMost/appstore-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 885 tokens to every session, about $0.0044 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
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.