Borrowing it
Nothing to install: this file belongs to web-casa/DeepSeek-Harness-Desktop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/web-casa/DeepSeek-Harness-Desktop/main/.agents/skills/asc-testflight-orchestration/SKILL.mdgit clone --depth 1 https://github.com/web-casa/DeepSeek-Harness-DesktopWrote 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/web-casa/deepseek-harness-desktop/asc-testflight-orchestration)<a href="https://agentmods.dev/skills/web-casa/deepseek-harness-desktop/asc-testflight-orchestration"><img src="https://agentmods.dev/badge/skills/web-casa/deepseek-harness-desktop/asc-testflight-orchestration/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/web-casa/deepseek-harness-desktop/asc-testflight-orchestration"><img src="https://agentmods.dev/badge/skills/web-casa/deepseek-harness-desktop/asc-testflight-orchestration.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00033 | $0.00540 |
| Opus 5 | $0.00016 | $0.00270 |
| Sonnet 5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
asc-testflight-orchestration 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 12d 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.
This is a copy
100% identical to asc-testflight-orchestration — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
asc TestFlight orchestration
Use this skill when managing TestFlight testers, groups, and build distribution.
Export current config
asc testflight config export --app "APP_ID" --output "./testflight.yaml"- Include builds/testers:
asc testflight config export --app "APP_ID" --output "./testflight.yaml" --include-builds --include-testers
Manage groups and testers
- Groups:
asc testflight groups list --app "APP_ID" --paginateasc testflight groups create --app "APP_ID" --name "Beta Testers"
- Testers:
asc testflight testers list --app "APP_ID" --paginateasc testflight testers add --app "APP_ID" --email "[email protected]" --group "Beta Testers"asc testflight testers invite --app "APP_ID" --email "[email protected]"
Distribute builds
asc builds add-groups --build-id "BUILD_ID" --group "GROUP_ID"- Remove from group:
asc builds remove-groups --build-id "BUILD_ID" --group "GROUP_ID" --confirm
Inspect a build's groups
asc testflight groups list --build-id "BUILD_ID" --output table- The build lookup is experimental. It resolves the app, paginates the app's groups, and includes groups with all-build access.
Upload without distribution
asc publish testflight --app "APP_ID" --ipa "./app.ipa" --upload-only --output json- Add
--waitwhen the next step needs a processed build. - Upload-only requires a new IPA or local Xcode build. Do not combine it with an existing
--build, groups, tester notifications, test notes, or beta-review submission.--build-numberis allowed as upload metadata, but it cannot be the only build input.
What to Test notes
asc builds test-notes create --build-id "BUILD_ID" --locale "en-US" --whats-new "Test instructions"asc builds test-notes update --localization-id "LOCALIZATION_ID" --whats-new "Updated notes"
Notes
- Use
--paginateon large groups/tester lists. - Prefer IDs for deterministic operations; use the ID resolver skill when needed.
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.
- 12d ago First seen · 45 lines · 33 tokens per session scan A 76e23e73ee6c
asc-testflight-orchestration is a skill published in the GitHub repository web-casa/DeepSeek-Harness-Desktop (121 stars, last pushed 7d ago), licensed MIT. It adds 33 tokens to every session and 540 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to asc-testflight-orchestration, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
qa-testing
Verify your work by actually operating the app or website you changed, instead of assuming it works. Strongly recommended whenever you build, modify, or debug a web app, website, or desktop GUI app. Drive real browsers with the agent-browser CLI and native desktop apps with the cua-driver CLI. These are installed on…
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
verify-ui-change-in-cloud
Verifies user-facing Warp client changes by spawning a cloud agent with computer use to test Warp. Use only when the user explicitly requested computer-use verification or accepted an offer to run it, and ONLY in non-sandboxed environments and local environments. Triggers a cloud agent that runs the test-warp-ui skill.
tauri-pilot
Inspect, interact with, and test a running Tauri v2 app via CLI. Communicates over Unix socket using JSON-RPC 2.0. Use when testing UI, automating interactions, or debugging a Tauri app.
dsh-testing
Design and run tests for DeepSeek Harness (dsh) changes — choosing the right tier (unit/coverage/e2e/snapshot/web), writing real-composition and smoke tests, snapshot record/refresh workflow, and coverage-gate rules in the deepseek-harness repo. Use this whenever the user adds or changes tests, asks which checks to…
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.