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/zmij/playstore-cli/claude-mdgit clone --depth 1 https://github.com/zmij/playstore-cliWhat 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.01424 | $0.01424 |
| Opus 5 | $0.00712 | $0.00712 |
| Sonnet 5 | $0.00285 | $0.00285 |
| Haiku 4.5 | $0.00142 | $0.00142 |
Grade A, and why
playstore-cli 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 2d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
playstore-cli — Agent Notes
Working on the CLI or the bundled MCP server. Stays here when this package is in a monorepo; ports cleanly when extracted to its own repo.
What this package is
A TypeScript CLI + MCP server for Google Play Console. Two binaries from one codebase:
playstore— interactive CLI (commander.js)playstore-mcp— Model Context Protocol server (stdio)
Both wrap src/client.ts, which wraps the googleapis androidpublisher_v3 surface.
Layout
| Module | Purpose |
|---|---|
src/index.ts |
CLI entry — registers commands from commands/ |
src/auth.ts |
Loads playstore-config.yaml, builds service-account auth context |
src/client.ts |
All Play API calls. Single source of truth |
src/project.ts |
getProjectRoot() / getWorktreeRoot() via git |
src/paths.ts |
Three configurable knobs (secrets, metadata, listings) |
src/types.ts |
YAML schema types (PlayIAPMetadata, ListingMetadata, etc.) |
src/commands/ |
iap, listings, screenshots, tracks, read |
src/mcp/server.ts |
MCP server — reuses client.ts, no duplication |
Rules
src/client.tsis the only file that calls the SDK. Add new ops there, not inside command files.- Don't shell out from the MCP server. Import
createClientand use its methods directly. - All path resolution goes through
paths.ts. Never hardcodel10n/metadata/play/...orl10n/metadata/google/...— usegetIapYamlPath(),getListingsDir(),getScreenshotsOrderPath(),getTracksBaseDir(). - Three path knobs because Play has a historical split. IAP YAML at
metadata_dir, listings + screenshots + release notes atlistings_dir. Downstream projects can unify by setting both to the same value. - Don't import from
auth.tsfor git roots. Useproject.tsdirectly. - Read calls that start an edit session must call
client.deleteEdit()afterwards if you're not going to commit. The MCP server does this religiously to avoid leaking pending edits across tool calls. - Lifecycle is separate from content.
iap synconly patches content (listings, prices, etc.) — state transitions happen viaiap stateand the dedicated client methods (activateBasePlan, etc.). - British spelling throughout (colour, localisation, etc.).
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.
- 2d ago First seen · 109 lines · 1,424 tokens per session scan A f76c1150e9b6
playstore-cli CLAUDE.md is an instructions file published in the GitHub repository zmij/playstore-cli (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,424 tokens to every session, about $0.0071 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.