Borrowing it
Nothing to install: this file belongs to hitosea/happy-next. 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/hitosea/happy-next/main/.claude/skills/happy-ios-build/SKILL.mdgit clone --depth 1 https://github.com/hitosea/happy-nextWrote 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/hitosea/happy-next/happy-ios-build)<a href="https://agentmods.dev/skills/hitosea/happy-next/happy-ios-build"><img src="https://agentmods.dev/badge/skills/hitosea/happy-next/happy-ios-build/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/hitosea/happy-next/happy-ios-build"><img src="https://agentmods.dev/badge/skills/hitosea/happy-next/happy-ios-build.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.00091 | $0.03723 |
| Opus 5.5 | $0.00036 | $0.01489 |
| Sonnet 5.5 | $0.00018 | $0.00745 |
| Haiku 4.5 | $0.00009 | $0.00372 |
Grade A, and why
happy-ios-build 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
happy-app iOS 测试包构建
在 Mac mini 上把 happy-app 打成 IPA，放进 ~/wwwroot/appdown/builds/，用户在 https://8083-weiyi.dootask.com/ 扫码安装。
| 模式 | 用户说法 | 产物 | 签名 / 推送 |
|---|---|---|---|
prod |
正式版、生产版、能收推送的 | HappyNext-<版本>-<构建号>-<sha>-<标签>-<时间>.ipa，com.hitosea.happy，带 Watch App |
EAS 上现有的 Ad Hoc 证书；主 App 和分享扩展用 EAS 上的描述文件，Watch App 和表盘组件用 iCloud 云盘 HappyNext/ios/ 里的描述文件；aps-environment=production，只能装在 Ad Hoc 描述文件里的设备上 |
dev |
开发版、调试版、dev client | HappyNextdev-<版本>-<sha>-<标签>-<时间>.ipa，com.hitosea.happy.dev，Debug 开发客户端，打开后要连 Metro，不含 Watch App |
Apple Development 证书 + 团队描述文件 com.hitosea.happy.dev 和 com.hitosea.happy.dev.share-extension，aps-environment=development |
真正的构建由仓库里的脚本完成，它们在 Mac mini 上运行：
scripts/build-prod.sh [标签]：正式版。从 EAS 拉 production 环境变量和 Ad Hoc 凭证，生产 prebuild，archive，导出，校验，发布。不管成功还是失败，都会还原开发用的 iOS 工程和eas.json，并删除临时凭证、钥匙串和描述文件。scripts/build-dev.sh [标签]：开发版。按需执行 yarn install、prebuild、pod install，然后不签名做 Debug 构建，再手动签名、打成 IPA 并发布。- 两个脚本最后都会输出
RESULT_*=行，汇报就以这些行为准。两个脚本共用一把锁，同时只能跑一个。
调用本技能，就等于授权执行下面「流程」里的全部操作，包括把 HEAD 推送到 origin/dev。流程之外的操作要单独确认。
流程
1. 确定模式和标签
- 模式：用户说了正式版或开发版就照着来；没说清楚就用 AskUserQuestion 问，给出「正式版」「开发版」两个选项。
- 标签：用 2–3 个英文词概括这次要测的内容（例如
stagebar、chat-scroll），会出现在文件名里。用户给了就用用户的。
2. 本地推送到 origin/dev
git status --porcelain --untracked-files=no
git push origin HEAD:dev
- 有未提交的已跟踪改动：停下来问用户，选项为「先提交再构建」和「只构建已提交的部分」。不要自己决定提交。
- push 被拒（origin/dev 有 HEAD 里没有的提交）：停下来，把
git log --oneline HEAD..origin/dev给用户看，问怎么处理。不要 force push。 - 记下
git rev-parse HEAD，第 3 步要用它核对。
3. Mac mini 拉到这个提交
先用 orchestrator_get_context 找到名为 Mac mini 的机器（要求 shellReady: true），再用 orchestrator_exec 执行：
cd ~/wwwroot/happy-next && git fetch -q origin \
&& if [ -n "$(git status --porcelain --untracked-files=no)" ]; then git stash push -q -m "happy-ios-build autostash $(date +%Y%m%d-%H%M%S)" && echo STASHED; fi \
&& { git switch -q dev 2>/dev/null || git switch -q -c dev --track origin/dev; } \
&& git merge -q --ff-only origin/dev && git rev-parse HEAD
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.
- 4d ago First seen · 117 lines · 91 tokens per session scan A ac238f0ffcc7
happy-ios-build is a skill published in the GitHub repository hitosea/happy-next (61 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 3,723 once invoked, about $0.0004 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-24.
Other skills, from other repositories
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
lov-mobile-adapt
A mobile adaptation workflow for existing web projects. It adjusts desktop websites for phones by handling responsive layouts, overflow, safe areas around notches, browser viewport height, touch targets, and mobile navigation.
lov-app-release
A release workflow for publishing one app version to declared channels such as iOS, Android, GitHub, a website, and documentation. It checks signing, build artifacts, and remote status rather than treating a successful build as a completed release.
apple-targets
Build, configure, and debug native Apple extension and target types (widgets, App Clips, share extensions, watchOS apps, Safari extensions, notification extensions, VPN/network extensions, and 40+ more) in an Expo app using the @bacons/apple-targets config plugin. Use when a user wants to add home screen presence…
android-ui-engineering
Use when building UI with Jetpack Compose. Covers component design, state hoisting, recomposition optimization, Material 3 theming, Navigation 3, adaptive layouts for large screens, previews, screenshot verification, and XML interop.
git-workflow-and-versioning
Use when managing branches, commits, versioning, and release workflows for Android projects, or when cutting a release, choosing a version bump, tagging, or writing a changelog. Covers trunk-based development, atomic commits, versionCode/versionName derived from tags, semver for library modules, changelogs and Play…