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 fiveonecode/agent-skills --skill xcode-cloudgit clone --depth 1 https://github.com/fiveonecode/agent-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/fiveonecode/agent-skills/xcode-cloud)<a href="https://agentmods.dev/skills/fiveonecode/agent-skills/xcode-cloud"><img src="https://agentmods.dev/badge/skills/fiveonecode/agent-skills/xcode-cloud/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/fiveonecode/agent-skills/xcode-cloud"><img src="https://agentmods.dev/badge/skills/fiveonecode/agent-skills/xcode-cloud.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.00057 | $0.00872 |
| Opus 5.5 | $0.00023 | $0.00349 |
| Sonnet 5.5 | $0.00011 | $0.00174 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade A, and why
xcode-cloud 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Xcode Cloud
Overview
Use Apple documentation as the authority for Xcode Cloud lifecycle behavior.
Keep this skill focused on workflow configuration, custom scripts, dependency
policy, and CI diagnosis. Use xcode-build for local build and simulator work,
and ios-xcodegen for XcodeGen project-spec semantics.
Quick Start
- Identify the
.xcodeprojor.xcworkspaceselected by the workflow. - Confirm that project or workspace is continuously present in the repository before configuring Xcode Cloud. A generated and ignored project is not a safe default.
- Confirm shared schemes, actions, Xcode version, dependency state, and the repository path used by the workflow.
- Add only the custom lifecycle scripts the workflow needs. Place executable
scripts in a top-level
ci_scriptsdirectory beside the selected project or workspace. - Make every script fail closed on missing inputs and verify the workflow in a disposable branch before rollout.
Apple Lifecycle Contract
Apple recognizes these executable top-level lifecycle names under
ci_scripts/:
ci_post_clone.shci_pre_xcodebuild.shci_post_xcodebuild.sh
The post-build script runs even when xcodebuild fails. Never infer success
from a missing exit code or action. Require the documented variables for the
selected action and reject missing, malformed, or failed state.
Keep logs free of secrets. Do not place credentials in remote URLs, command arguments, or echoed environment dumps.
XcodeGen Exception
Do not use post-clone generation to create the project or workspace Xcode Cloud needs for initial configuration. Prefer committing the generated project when the repository deliberately uses XcodeGen.
Use regeneration during a build only as a separately reviewed exception. The
repository must prove the selected Xcode and XcodeGen versions with a fixture,
own deterministic tool acquisition, and keep the expected project continuously
present. assets/ci_pre_xcodebuild.sh is an opt-in guard for that exception:
What ships with it
3 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 · 91 lines · 57 tokens per session scan A 35f176995397
xcode-cloud is a skill published in the GitHub repository fiveonecode/agent-skills (19 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 872 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
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…