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 sonature-lab/timsquad --skill ci-cdgit clone --depth 1 https://github.com/sonature-lab/timsquadWrote 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/sonature-lab/timsquad/ci-cd)<a href="https://agentmods.dev/skills/sonature-lab/timsquad/ci-cd"><img src="https://agentmods.dev/badge/skills/sonature-lab/timsquad/ci-cd/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/sonature-lab/timsquad/ci-cd"><img src="https://agentmods.dev/badge/skills/sonature-lab/timsquad/ci-cd.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.00042 | $0.01189 |
| Opus 5.5 | $0.00017 | $0.00476 |
| Sonnet 5.5 | $0.00008 | $0.00238 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
ci-cd 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Pipeline
Flutter 앱의 빌드, 테스트, 서명, 배포 자동화 가이드. iOS/Android 코드 서명, Fastlane/Codemagic/GitHub Actions 파이프라인, 스토어 배포, 버전 관리.
Philosophy
- 배포는 자동 — 수동 빌드/업로드 금지, CI가 전부 처리
- 서명은 분리 — 코드 서명 키를 CI 환경에 안전하게 주입, 레포에 절대 포함 금지
- 버전은 규칙 — 시맨틱 버저닝 + 빌드 넘버 자동 증가
- 환경은 격리 — dev/staging/prod 설정 분리, 환경별 독립 파이프라인
Resources
6개 규칙 + 1개 참조. CI/CD 파이프라인 전체를 커버.
| Priority | Type | Resource | Description |
|---|---|---|---|
| CRITICAL | rule | code-signing | iOS provisioning profile, Android keystore, 인증서 관리 |
| HIGH | rule | fastlane-setup | Fastfile 구성, match, supply, deliver, .env 관리 |
| HIGH | rule | codemagic-setup | codemagic.yaml 워크플로우, 환경변수, 빌드 트리거 |
| HIGH | rule | github-actions | Flutter 빌드 워크플로우, 테스트-빌드-업로드 파이프라인 |
| HIGH | rule | store-deployment | TestFlight, Play Store tracks, 메타데이터, 단계적 출시 |
| MEDIUM | rule | versioning | 시맨틱 버저닝, 빌드 넘버 자동 증가, CHANGELOG, git 태그 |
| — | ref | ci-cd-pipeline | 파이프라인 아키텍처, 환경 설정, 시크릿 관리, 롤백 |
Quick Rules
코드 서명
- iOS:
match로 인증서/프로필 Git 저장소 관리 (팀 공유) - Android: keystore 파일을 CI 환경변수로 base64 주입
- 개발용/배포용 인증서 분리 — 동일 인증서 사용 금지
- 서명 키를 레포에 커밋 금지 —
.gitignore에*.keystore,*.jks,*.p12추가
Fastlane
Fastfile에ios/android레인 분리match→ iOS 인증서 자동 관리 (Git 저장소 or Google Cloud Storage)supply→ Google Play 업로드,deliver→ App Store 업로드.env로 환경별 설정 분리 (.env.production,.env.staging)
CI/CD 플랫폼
- Codemagic: Flutter 네이티브 지원,
codemagic.yaml로 워크플로우 정의 - GitHub Actions:
subosito/flutter-action으로 Flutter 설치, pub cache 캐시 필수 - 빌드 트리거: 태그 푸시 (
v*) → 릴리스, PR → 테스트만
스토어 배포
- TestFlight:
deliver또는app-store-connectAPI로 업로드 - Play Store: internal → closed → open → production 트랙 순서
- 단계적 출시 (staged rollout): 1% → 5% → 20% → 50% → 100%
- 메타데이터 (스크린샷, 설명) 코드로 관리 (
fastlane/metadata/)
What ships with it
7 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.
- 1mo ago First seen · 83 lines · 42 tokens per session scan A 5ca382a7f5be
ci-cd is a skill published in the GitHub repository sonature-lab/timsquad (12 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 1,189 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-08-30.
Other skills, from other repositories
mobile-ci-cd
Automate mobile app build, test, and deployment pipelines for iOS and Android using Fastlane, EAS Build, or GitHub Actions.
github-workflow-automation
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management.
android-tooling
Configure Android static analysis with Detekt, Ktlint, and Android Lint for CI/CD quality gates. Use for Android-specific lint and quality tooling; defer generic Java Checkstyle, SonarQube, and standalone CI configuration.
github-workflow-automation
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management.
app-store-deploy
Use when a mobile app needs a release pipeline - fastlane GitHub Actions to TestFlight (iOS) and Play internal track (Android), with code signing and the release naming that maps to TaskTrooper's prod deploy.
cicd-expert
Expert-level CI/CD with GitHub Actions, Jenkins, deployment pipelines, and automation. Use when the user mentions CI/CD, GitHub Actions, Jenkins, GitLab CI, deployment, or automation, or when the task involves CI/CD Fundamentals, Pipeline Design, Workflow Basics, or Docker Build and Push.