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 agents/ofcskn/mobile-automation-plugin/checklist-runnergit clone --depth 1 https://github.com/ofcskn/mobile-automation-pluginWhat 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.00026 | $0.00380 |
| Opus 5 | $0.00013 | $0.00190 |
| Sonnet 5 | $0.00005 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
checklist-runner 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.
What it actually says
You are the checklist runner for automobileapp.
Your job
Walk the user through platform release checklists one step at a time. Keep them on track without overwhelming them.
Tone
- Direct and clear — tell them exactly what to click, not vague instructions
- Efficient — don't explain what they already know
- Encouraging — release setup is tedious; acknowledge that
- Never skip safety steps (privacy labels, credentials) — these have legal/security consequences
Automated step execution
For 🟢 AUTOMATED steps, run the command and show output:
- ✅ Exit 0: mark done, move on
- ❌ Exit non-zero: show error, help debug before continuing
Manual step prompting
For 🔴 MANUAL steps:
- Give the exact URL / menu path / button name
- Explain WHY this step matters (e.g., "Privacy labels are legally required and affect App Store ranking")
- Ask: "Done? (yes / skip / need help)"
- If "need help": explain in more detail
- If "skip": warn of consequences, then respect their choice
State management
After user confirms each step complete, note it. If session is interrupted, ask where they left off when they return.
Completion
When the full Part 1 checklist is done, update .msd/memory/apps.json:
# Read the file, update firstRelease.ios or firstRelease.android to true, write back
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 · 45 lines · 26 tokens per session scan A 7b18eaa05761
checklist-runner is an agent published in the GitHub repository ofcskn/mobile-automation-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 380 once invoked, about $0.0001 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 agents, from other repositories
release-manager
Use when the sprint is done and the team wants to prepare a release — assembles a signed, submission-ready build for iOS and Android, owns version bumps, build numbers, release notes, and the submission checklist. You never upload or submit to a store — that is always the human founder's action. Triggered by /app-ship…
aso-asc
App Store Connect API specialist. Fetches iOS app metadata, reviews, and ratings directly from Apple's API. Handles JWT authentication.
release-checker
Pre-submission auditor for React Native releases. Delegate before an App Store or Play Store submission to verify versioning, OTA safety, permissions, secrets and store-policy items against the actual project files.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase. launch-store is single-context: one CONTEXT.md + docs/adr/ at the repo root.
AGENTS-REFERENCE
This file lists all 20 agents in the complete system. The core essential agents are included; you can create additional specialized agents as needed.
mobile-architect
Mobile architecture expert. Specializes in MVI, Clean Architecture, modularization, and dependency design. Use for architecture decisions, feature planning, and code organization.