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 makifbaysal/tasktrooper --skill app-store-deploygit clone --depth 1 https://github.com/makifbaysal/tasktrooperWrote 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/makifbaysal/tasktrooper/app-store-deploy)<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/app-store-deploy"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/app-store-deploy/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/makifbaysal/tasktrooper/app-store-deploy"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/app-store-deploy.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.00050 | $0.01840 |
| Opus 5.5 | $0.00020 | $0.00736 |
| Sonnet 5.5 | $0.00010 | $0.00368 |
| Haiku 4.5 | $0.00005 | $0.00184 |
Grade A, and why
app-store-deploy 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Store Deploy (mobile)
Overview
Mobile does not deploy to a cloud you run — it deploys to Apple's and Google's stores, so there is no GCP/AWS split. The CD pipeline builds a signed artifact and uploads it to a test track (TestFlight / Play internal), which is the mobile equivalent of a staged deploy. Read [[ci-cd-pipeline-authoring]] for the workflow naming/dispatch contract; this skill fills in the store steps.
Core principle: Signing is the hard part, not the upload. Get reproducible, secret-driven signing right and the release is a one-command fastlane lane.
Set up the pipeline
If the repo has no fastlane/ yet, create it directly: Fastfile lanes beta (stage) and release (prod, store-executor driven), per the iOS/Android sections below, plus deploy-stage/preprod/prod.yml workflow files. There is no search_boilerplate_catalog tool in this agent's tool list — don't call it.
Environment mapping
stage→ internal test track: TestFlight (iOS) / Play internal track (Android).preprod→ TestFlight external group / Play closed (beta) track.prod→ App Store / Play production — the workflow file must still containprod/production/releaseso the pipeline'sprod_deploycheck detects it, but nothing dispatches it directly: mobile ships through abatchdelivery profile. A merged mobile task joins the component's draft release and waits indone; a human cuts the release on the Deploy tab, and the release engineer then starts the build (storeexecutor) or lets a tag push trigger it (github_actionsexecutor — see [[ci-cd-pipeline-authoring]]'s batch section).
iOS — TestFlight
- Build on a macOS runner (
runs-on: macos-26;macos-14is deprecated since 2026-07-06 and unsupported from 2026-11-02, and cannot run Xcode 26, which every App Store Connect upload has needed since 2026-04-28). Select the Xcode version the app needs (≥26) withxcode-select/xcodes; Xcode 27 needs macOS Tahoe 26.6+ on the runner image. - Signing via fastlane match (certs/profiles in a private git repo, decrypted with
MATCH_PASSWORD) — never check certificates into the app repo. - Auth to App Store Connect with an API key (
.p8+ key id + issuer id), not an Apple ID password. - Lane:
fastlane build_app→upload_to_testflight. For prod, submit for review (fastlane deliver).
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 Changed · +4 lines 0596f2857a21
- 8d ago First seen · 74 lines · 50 tokens per session scan A 3cf7b4a630d3
app-store-deploy is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 1,840 once invoked, about $0.0002 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-10-05.
Other skills, from other repositories
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
render
Use when deploying or fixing an app on Render — web services, background workers, cron jobs, private services, managed Postgres and Key-Value, and especially the render.yaml Blueprint. Covers deploys that fail with no open ports detected, 502s on first deploy, free-tier cold starts, and a free Postgres about to expire…
flutter-cicd
Set up CI/CD pipelines for Flutter apps. Use when configuring automated testing, build, or deployment workflows with GitHub Actions or Fastlane.
touch-release
Set up mobile release pipeline — Fastlane, code signing, CI, beta distribution, versioning. Use when asked about "app store setup", "release pipeline", "fastlane", "beta distribution", or "signing".
ci-cd
A guide for automating the process of building, testing, signing, and publishing Flutter mobile apps. It covers both iOS and Android release workflows.
loop-triage
Triage recent CI failures, open issues, and recent commits into a prioritized, actionable picture. Reads the prior STATE.md as memory and rewrites it. The maker half of the loop.