msd-setup-credentials

An interactive setup command for production credentials used to submit apps to the Apple App Store and Google Play, with storage in EAS secrets or a local production environment file.

In plain words
What is it for?
Use it to configure an Expo access token, App Store Connect credentials, and Android store credentials for local or continuous-integration releases.
Why use it?
It guides you through obtaining the required keys, checks their format, and places them where the release process can use them.

Command

Part of the automobileapp plugin — 11 skills, 17 commands, 9 agents shipped together

Install

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.

agentmods
npx agentmods add commands/ofcskn/mobile-automation-plugin/msd-setup-credentials
Clone the repo
git clone --depth 1 https://github.com/ofcskn/mobile-automation-plugin

Or install automobileapp, the plugin that ships this one along with the rest of its 11 skills, 17 commands, 9 agents.

Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,383 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00030 $0.01383
Opus 5 $0.00015 $0.00691
Sonnet 5 $0.00006 $0.00277
Haiku 4.5 $0.00003 $0.00138

Measured 2d ago against content hash cd160bfe32a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

msd-setup-credentials 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.

commands/msd-setup-credentials.md · 168 lines

How it starts

The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Set up production credentials for store submission.

Load skills/submitting-app-release/references/credentials-guide.md before starting.


Step 1 — Choose storage path

Ask:

"Where should credentials be stored?

  • EAS secrets (recommended) — encrypted in EAS cloud. Works in CI, GitHub Actions, and locally. Set once, works forever. Run eas secret:list anytime to verify.
  • Local .env.production — stored in a local file. Faster to set up. Not available in CI unless you add it to your pipeline."

Step 2 — EXPO_TOKEN (required for both platforms)

Ask: "Do you have an Expo access token set? (check with eas whoami)"

If not:

  1. Direct user to: expo.dev → Account → Settings → Access Tokens → Create Token
  2. Ask user to paste the token (it starts with expo_)
  3. Validate format: must start with expo_ and be at least 20 chars
  4. Store it:
# EAS secrets path
eas secret:create --scope project --name EXPO_TOKEN --value "<token>"

# Local path
echo 'EXPO_TOKEN=<token>' >> .env.production

Step 3 — iOS credentials (skip if Android-only)

App Store Connect API Key

  1. Direct user to: App Store Connect → Users and Access → Integrations → App Store Connect API → Generate API Key

    • Role: App Manager or higher
    • Download the .p8 file — it can only be downloaded once
  2. Collect three values:

APP_STORE_CONNECT_API_KEY_ID   — shown on the key list (10 alphanumeric chars)
APP_STORE_CONNECT_ISSUER_ID    — shown above the key list (UUID format)
APP_STORE_CONNECT_API_KEY_CONTENT — base64 of the .p8 file
  1. Generate the base64 content:
base64 -i AuthKey_XXXXXXXXXX.p8
# Copy the output — that is APP_STORE_CONNECT_API_KEY_CONTENT
  1. Validate each value before storing:
# Key ID: 10 alphanumeric chars
echo "KEYID" | grep -E '^[A-Z0-9]{10}$' && echo "✅ format valid" || echo "❌ invalid"

# Issuer ID: UUID
echo "ISSUERID" | grep -E '^[0-9a-f]{8}-([0-9a-f]{4}-){3}[0-9a-f]{12}$' && echo "✅ format valid" || echo "❌ invalid"

# Key content: must contain PEM header
echo "CONTENT" | grep "BEGIN PRIVATE KEY" && echo "✅ valid" || echo "❌ missing PEM header"

Read the full file on GitHub · 168 lines

Changes

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.

  1. 2d ago First seen · 168 lines · 30 tokens per session scan A cd160bfe32a2

Subscribe to this mod's changes

msd-setup-credentials is a command published in the GitHub repository ofcskn/mobile-automation-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 1,383 once invoked, about $0.0002 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.