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 skills/robertguss/claude-code-toolkit/mobile-app-launch-checklistnpx skills add robertguss/claude-code-toolkit --skill mobile-app-launch-checklistgit clone --depth 1 https://github.com/robertguss/claude-code-toolkitWrote 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/skills/robertguss/claude-code-toolkit/mobile-app-launch-checklist)<a href="https://agentmods.dev/skills/robertguss/claude-code-toolkit/mobile-app-launch-checklist"><img src="https://agentmods.dev/badge/skills/robertguss/claude-code-toolkit/mobile-app-launch-checklist.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.00131 | $0.02838 |
| Opus 5 | $0.00066 | $0.01419 |
| Sonnet 5 | $0.00026 | $0.00568 |
| Haiku 4.5 | $0.00013 | $0.00284 |
Grade A, and why
mobile-app-launch-checklist 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 5d 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile App Launch Checklist
Generate a structured, actionable launch checklist tailored to the user's app, target platform(s), and timeline. Walk through each phase sequentially, confirm completion of critical items, and flag blockers.
Inputs
| Input | Required | Description | Default |
|---|---|---|---|
| App name | Yes | Name of the app being launched | — |
| Platform | Yes | iOS, Android, or both | Both |
| Launch date | No | Target launch date | 4 weeks from today |
| App type | No | Free, freemium, paid, subscription | Freemium |
Ask for these inputs before generating the checklist. Adjust timelines and requirements based on the target platform.
Phase 1: Pre-Submission Preparation (2-4 Weeks Before)
App Quality
- Crash-free rate exceeds 99.5% across all supported devices
- All core user flows tested end-to-end (onboarding, purchase, key features)
- Performance benchmarks met:
- Cold launch under 2 seconds
- Smooth scrolling at 60fps
- Memory usage within platform limits
- Battery impact acceptable (no background drain)
- Accessibility audit complete (VoiceOver/TalkBack, Dynamic Type, contrast)
- Offline behavior handled gracefully (error states, cached data)
- Edge cases tested: no network, low storage, permissions denied, interruptions
Privacy & Compliance
- Privacy policy URL live and accessible
- iOS: App Tracking Transparency prompt implemented (if tracking)
- Android: Data safety section completed in Google Play Console
- GDPR compliance verified (if serving EU users): consent flows, data deletion
- CCPA compliance verified (if serving California users)
- Data collection accurately declared on both platforms
- Third-party SDK privacy policies reviewed
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 302 lines · 131 tokens per session scan A d9280b281b15
mobile-app-launch-checklist is a skill published in the GitHub repository robertguss/claude-code-toolkit (108 stars, last pushed 27d ago), licensed MIT. It adds 131 tokens to every session and 2,838 once invoked, about $0.0007 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-30.
Other skills, from other repositories
offensive-mobile
Mobile (Android + iOS) application penetration testing methodology. Covers static analysis (apktool/jadx for Android, class-dump/Hopper/IDA for iOS), dynamic instrumentation with Frida and Objection, SSL pinning bypass strategies, root/jailbreak detection bypass, deep-link / URL-scheme abuse, exported component…
offensive-vuln-classes
Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…
offensive-edr-evasion
EDR evasion offensive checklist: hook unhooking (user/kernel), direct syscalls, PPID spoofing, process injection variants, AMSI bypass, ETW patching, memory encryption, and behavior-based evasion. Use when planning EDR bypass during red team engagements or researching AV/EDR evasion techniques.
offensive-mitigations
Security mitigation reference and bypass catalog: ASLR, DEP/NX, RELRO, stack canaries, CFI, sandboxing, seccomp. Covers both detection of enabled mitigations and known bypass techniques. Use when assessing target hardening or planning exploit mitigation bypasses.
offensive-exploit-development
Exploit development operational guide: environment setup, debugging workflow, PoC development lifecycle, writing reliable exploits, using pwntools/pwndbg, heap exploitation techniques, and weaponization considerations. Use when actively developing exploits or setting up an exploit dev environment.
offensive-tls-attacks
Comprehensive methodology for auditing and exploiting TLS/SSL implementations and misconfigurations across network services and mobile applications. Covers protocol downgrade attacks including POODLE (CVE-2014-3566) against SSLv3 CBC padding, DROWN (CVE-2016-0800) cross-protocol attack leveraging SSLv2 export ciphers…