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/zelentsov-dev/apple-ads-mcp/claude-mdgit clone --depth 1 https://github.com/zelentsov-dev/apple-ads-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/zelentsov-dev/apple-ads-mcp/claude-md)<a href="https://agentmods.dev/instructions/zelentsov-dev/apple-ads-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/zelentsov-dev/apple-ads-mcp/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 | $0.00474 | $0.00474 |
| Opus 5 | $0.00237 | $0.00237 |
| Sonnet 5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
apple-ads-mcp 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 4d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apple Ads MCP
Product
apple-ads-mcp is a public, local-first Model Context Protocol server for the Apple Ads Platform API v1. It supports App Store advertising only. Apple Maps and the legacy Campaign Management API v5 are out of scope.
The project is independent and is not affiliated with, endorsed by, or sponsored by Apple Inc.
Architecture
- Go 1.26.7+
- Official MCP Go SDK
cmd/apple-ads-mcpcontains only CLI wiring- Production code lives under
internal/ stdoutis reserved for MCP JSON-RPC; diagnostics go tostderr- Production Apple API and OAuth base URLs are fixed constants
- Credentials remain local and tokens are cached only in memory
Safety
- The default server mode is read-only.
- Write access requires the server flag, profile permission, Apple role, preview, and a single-use receipt.
- Never add a raw HTTP passthrough tool.
- Never log private keys, client secrets, access tokens, authorization headers, or request bodies containing credentials.
- Read operations may retry bounded transient failures. Mutations must not retry after an ambiguous transport failure.
- Identifiers and decimal money amounts remain strings in public MCP schemas.
Consumer setup
- Treat
README.mdas the canonical public installation and onboarding guide. - Prefer
brew install zelentsov-dev/tap/apple-ads-mcpon macOS and Linux. - Register GUI MCP clients with the absolute Homebrew binary path; do not assume they inherit an interactive shell's
PATH. - The bundled plugin manifest,
.mcp.json, and skill metadata do not install the executable or grant Apple Ads access by themselves. - Never ask a user to paste private-key contents, access tokens, or client secrets into a conversation.
- Keep setup and connection checks read-only. Do not enable write or delete gates unless the user's current request explicitly authorizes mutations.
Development
- Use idiomatic Go and wrap errors with context.
- Keep exported surface area small; prefer
internal/packages. - Add table-driven tests for validation and failure behavior.
- Run
go test ./...,go vet ./..., skill validation, and plugin validation before handoff. - Do not perform live Apple Ads mutations from automated tests.
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.
- 4d ago First seen · 44 lines · 474 tokens per session scan A 8932647d1e14
apple-ads-mcp CLAUDE.md is an instructions file published in the GitHub repository zelentsov-dev/apple-ads-mcp (4 stars, last pushed today), licensed MIT. It adds 474 tokens to every session, about $0.0024 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
storeshots-mcp AGENTS.md
Instructions for mtbun/storeshots-mcp, covering agents.md, what this project is, architecture, non-negotiable principles and layout contract (compose).
appshot AGENTS.md
Instructions for trunghaiy/appshot, covering agents.md, repository overview, architecture, repository structure and agent skills specification.
appshot CLAUDE.md
Instructions for trunghaiy/appshot, covering appshot — claude code project brief, key constraint, where things live, build and git.
storeshots-mcp CLAUDE.md
Instructions for mtbun/storeshots-mcp, a project described as: Store-ready App Store & Google Play screenshots from any MCP client. Device frames, benefit-driven headlines, exact store dimensions. No API keys.
ollama CLAUDE.md
Claude Code instructions for ollama/ollama: See AGENTS.md for the shared agent instructions for this repository.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.