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 skills add rshankras/claude-code-apple-skills --skill beta-testinggit clone --depth 1 https://github.com/rshankras/claude-code-apple-skillsWrote 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/rshankras/claude-code-apple-skills/beta-testing)<a href="https://agentmods.dev/skills/rshankras/claude-code-apple-skills/beta-testing"><img src="https://agentmods.dev/badge/skills/rshankras/claude-code-apple-skills/beta-testing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rshankras/claude-code-apple-skills/beta-testing"><img src="https://agentmods.dev/badge/skills/rshankras/claude-code-apple-skills/beta-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 327 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00067 | $0.04733 |
| Opus 5.5 | $0.00027 | $0.01893 |
| Sonnet 5.5 | $0.00013 | $0.00947 |
| Haiku 4.5 | $0.00007 | $0.00473 |
Grade A, and why
beta-testing 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 1mo 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 — 502 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beta Testing Strategy
End-to-end beta testing workflow for Apple platform apps — from TestFlight setup through feedback collection to launch readiness decision.
When This Skill Activates
Use this skill when the user:
- Wants to run a beta test or plan a beta program
- Needs to set up TestFlight for internal or external testing
- Asks how to collect user feedback during beta
- Wants to know if their app is ready to launch
- Needs help designing a beta feedback survey
- Asks "how many beta testers do I need?"
- Mentions "TestFlight", "beta testers", "soft launch", or "launch readiness"
- Wants to plan a structured beta rollout
- Needs a go/no-go framework for shipping
Process
Phase 1: TestFlight Program Strategy
Before recruiting testers, understand Apple's two-tier beta system.
Internal Testing
| Attribute | Details |
|---|---|
| Max testers | 100 team members, each on up to 30 devices |
| App Review required | No |
| Build availability | Immediate after upload — enable Automatic Distribution so every new build reaches the group without manual selection |
| Tester requirement | Must be App Store Connect users |
| Best for | Team, close collaborators, developer friends |
| Expiration | 90 days from build upload |
Use internal testing for:
- Catching crashes and obvious bugs before anyone else sees the app
- Validating core flows work end-to-end
- Getting feedback from people who will be honest (friends, fellow devs)
External Testing
| Attribute | Details |
|---|---|
| Max testers | 10,000 |
| App Review required | Yes — the first build (and builds with significant changes) pass Beta App Review, usually 24-48 hours |
| Build availability | After Beta App Review approval |
| Tester requirement | Anyone with an email address and iOS/macOS device |
| Best for | Real users, broader audience, validating product-market fit |
| Expiration | 90 days from build upload — plan your build cadence around it |
Use external testing for:
- Validating with real users who have no context about your app
- Stress-testing with diverse devices, OS versions, and usage patterns
- Gathering signal on whether the value proposition resonates
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.
- 1mo ago First seen · 502 lines · 67 tokens per session scan A 329e53f510f1
beta-testing is a skill published in the GitHub repository rshankras/claude-code-apple-skills (816 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 4,733 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
ios-screenshot-taker
Use when capturing deterministic iOS simulator screenshots for App Store, TestFlight, QA, launch pages, or marketing decks. Covers xcodebuild build, simulator boot/install/launch, seeded demo states, xcrun simctl screenshots, required App Store device classes, public-safe output handling, and slash commands such as…
ui-crawler-max
Autonomous UI crawler for iOS simulator apps — rapid, element-precise data collection. Use whenever the user says "crawl my app", "auto-test the UI", "click/tap through every screen", "monkey test", "explore the app and find errors/crashes", "collect screenshots of all screens", "smoke test the whole app", or asks for…
swift-protocol-di-testing
Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
ios-development
Comprehensive guide for building native Apple platform applications.