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/timheuer/copilot-instructions/ios-cicd-github-actionsnpx skills add timheuer/copilot-instructions --skill ios-cicd-github-actionsgit clone --depth 1 https://github.com/timheuer/copilot-instructionsWrote 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/timheuer/copilot-instructions/ios-cicd-github-actions)<a href="https://agentmods.dev/skills/timheuer/copilot-instructions/ios-cicd-github-actions"><img src="https://agentmods.dev/badge/skills/timheuer/copilot-instructions/ios-cicd-github-actions.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.00053 | $0.01257 |
| Opus 5 | $0.00026 | $0.00629 |
| Sonnet 5 | $0.00011 | $0.00251 |
| Haiku 4.5 | $0.00005 | $0.00126 |
Grade A, and why
ios-cicd-github-actions 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 4d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS CI/CD with GitHub Actions (Build, Sign, Upload)
This skill helps design, implement, and debug a framework-agnostic iOS CI/CD pipeline using GitHub Actions. It focuses on the essential Apple requirements: build environment, signing, provisioning, archiving, and TestFlight upload.
What “done” looks like
A GitHub Actions workflow that:
- Uses a pinned macOS runner
- Uses a pinned Xcode version
- Imports an Apple Distribution certificate into a temporary keychain
- Downloads App Store provisioning profiles using App Store Connect API keys
- Builds a Release archive and exports an IPA
- Uploads the IPA to TestFlight
Canonical CI/CD order (do not reorder)
1. Pin the build environment
- Explicit
runs-on(nevermacos-latest) - Explicit Xcode version
- Set a job timeout
2. Checkout source
- Use
actions/checkout - Enable submodules if required
3. Install build dependencies
- Language SDKs, CLIs, package managers
- Restore dependencies deterministically (lockfiles)
4. Import signing certificate
- Use an Apple Distribution
.p12 - Import into a temporary keychain
- Never store raw certificates in the repo
5. Download provisioning profiles
- Use App Store Connect API key authentication
- Match bundle identifier exactly
- Use
IOS_APP_STOREprofile type for TestFlight
6. Build, archive, export IPA
- Build in Release
- Produce an
.ipasuitable for App Store distribution - Export to a predictable path
7. Upload to TestFlight
- Authenticate with the same App Store Connect API key
- Ensure build number is valid and incremented
Required GitHub Secrets
Apple Distribution Certificate
APPSTORE_CERTIFICATE_P12– base64-encoded.p12APPSTORE_CERTIFICATE_P12_PASSWORD– password for the.p12
App Store Connect API
APPSTORE_ISSUER_IDAPPSTORE_KEY_IDAPPSTORE_PRIVATE_KEY– contents of the.p8file
App Metadata
IOS_BUNDLE_ID– e.g.com.example.myapp
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.
- 4d ago First seen · 192 lines · 0 tokens per session scan A 1862a95555ed
ios-cicd-github-actions is a skill published in the GitHub repository timheuer/copilot-instructions (1 stars, last pushed 7mo ago), licensed MIT. It adds 53 tokens to every session and 1,257 once invoked, about $0.0003 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 skills, from other repositories
compose-graphics
Advanced Compose visuals - Material 3 Expressive motion physics, AGSL shaders (Android 13+), Canvas/DrawScope generative, graphicsLayer effects.
compose-multiplatform
Compose Multiplatform / KMP patterns - expect/actual composables, platform-specific code, density and font handling cross-target, iOS/Android/Desktop interop.
swiftui-graphics
Advanced SwiftUI visuals - Metal shaders (.colorEffect, .layerEffect, .distortionEffect), .visualEffect, Liquid Glass (iOS 26), Canvas, holographic and CRT effects.
cast
Cast genjutsu on a UI - creative coding for motion, micro-interactions, and wow-factor. Scans the stack, proposes an interaction thesis, loads the right sub-skills, implements the illusion. Adapts to Web, Android (Compose), Apple (SwiftUI).
github-actions
GitHub Actions workflow patterns for React Native iOS simulator and Android emulator cloud builds with downloadable artifacts. Use when setting up CI build pipelines or downloading GitHub Actions artifacts via gh CLI and GitHub API.
expo-cicd-workflows
Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI/CD or workflows in an Expo or EAS context, mentions .eas/workflows/, or wants help with EAS build pipelines or deployment automation.