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/vvlladd/appstoreconnectmcp/claude-mdgit clone --depth 1 https://github.com/Vvlladd/AppStoreConnectMCPWrote 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/vvlladd/appstoreconnectmcp/claude-md)<a href="https://agentmods.dev/instructions/vvlladd/appstoreconnectmcp/claude-md"><img src="https://agentmods.dev/badge/instructions/vvlladd/appstoreconnectmcp/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.00870 | $0.00870 |
| Opus 5 | $0.00435 | $0.00435 |
| Sonnet 5 | $0.00174 | $0.00174 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
AppStoreConnectMCP 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Store Connect MCP Server
Project Overview
A Swift MCP (Model Context Protocol) server that exposes App Store Connect REST API operations as tools for AI agents. Built as a macOS command-line tool using Tuist for project generation.
Tech Stack
- Language: Swift 6.0 (strict concurrency)
- Build system: Tuist 4.x (
Project.swift,Tuist/Package.swift) - Dependencies: MCP Swift SDK (
modelcontextprotocol/swift-sdk0.7.1+) - Platform: macOS 13+
- Auth: ES256 JWT signing via Apple CryptoKit
Architecture
Sources/AppStoreConnectMCP/
main.swift — Entry point: server setup + stdio transport
Configuration.swift — Loads env vars (single + multi-org)
OrganizationRegistry.swift — Multi-org registry (actor)
Auth/JWTGenerator.swift — JWT token generation
Logging/MCPLogger.swift — Stderr-based structured log handler
API/
AppStoreConnectClient.swift — HTTP client with auto-retry on 401/429
Endpoints.swift — URL builders
Models/ — Codable request/response types (JSON:API format)
Tools/
ToolDefinitions.swift — MCP tool schemas (JSON Schema)
ToolRouter.swift — Dispatches tool calls to handlers via OrganizationRegistry
Handlers/ — One handler per tool
Available MCP Tools
list_apps, create_version, list_versions, update_version, set_phased_release, add_localization, list_builds, upload_build, attach_build, prepare_release, release_status, clone_version_metadata, validate_for_submission, submit_for_review, release_version, list_diagnostic_signatures, get_diagnostic_logs, get_perf_metrics, list_orgs, set_default_org
All tools (except list_orgs and set_default_org) accept an optional org parameter to target a specific organization.
Build & Run
tuist install # Fetch dependencies
tuist generate # Generate Xcode project
tuist build # Build via CLI
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 · 91 lines · 870 tokens per session scan A 9718bdf3ce8d
AppStoreConnectMCP CLAUDE.md is an instructions file published in the GitHub repository Vvlladd/AppStoreConnectMCP (8 stars, last pushed 1mo ago), licensed MIT. It adds 870 tokens to every session, about $0.0043 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).
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 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).
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.
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.
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.