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 CH3COOH/claude-skills --skill ios-bump-versiongit clone --depth 1 https://github.com/CH3COOH/claude-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/ch3cooh/claude-skills/ios-bump-version)<a href="https://agentmods.dev/skills/ch3cooh/claude-skills/ios-bump-version"><img src="https://agentmods.dev/badge/skills/ch3cooh/claude-skills/ios-bump-version/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/ch3cooh/claude-skills/ios-bump-version"><img src="https://agentmods.dev/badge/skills/ch3cooh/claude-skills/ios-bump-version.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.00085 | $0.01098 |
| Opus 5 | $0.00043 | $0.00549 |
| Sonnet 5 | $0.00017 | $0.00220 |
| Haiku 4.5 | $0.00009 | $0.00110 |
Grade A, and why
ios-bump-version 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 11d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump Version スキル
iOSアプリ の MARKETING_VERSION を更新し、リリースブランチへのコミットまで自動実行します。
事前バリデーション
以下を確認し、問題があれば処理を中断してユーザーに案内すること。
| チェック項目 | 確認コマンド | 問題がある場合 |
|---|---|---|
| 引数の有無 | - | 新バージョン番号を確認する |
| バージョン形式 | - | X.X.X 形式（数字とドット）でなければ拒否 |
| 作業ディレクトリ | git status --porcelain |
未コミット変更があれば先に commit/stash を案内 |
| 現在のブランチ | git branch --show-current |
release-vX.X.X・release-vX.X.X-feature/*・develop・master のいずれかであることを確認。それ以外は処理を中断する |
| 現在のバージョン | grep -n "MARKETING_VERSION" *.xcodeproj/project.pbxproj |
目標バージョンと同一なら「既に最新です」と警告して終了 |
手順
ここでは例として MyApp というアプリのバージョンを修正する。
Step 1: 現在の状態を確認
git branch --show-current
git status --porcelain
現在のバージョンを確認する：
grep -n "MARKETING_VERSION" MyApp.xcodeproj/project.pbxproj
Step 2: フィーチャーブランチを作成
現在のブランチ名に応じてブランチ名を決定する。
ケース 1: release-vX.X.X 形式のリリースブランチ上（通常）:
git checkout -b release-v<base-version>-feature/bump-up-to-v<new-version>
例: ベースが release-v2.9.10、新バージョンが 2.9.10 の場合
git checkout -b release-v2.9.10-feature/bump-up-to-v2.9.10
ケース 2: release-vX.X.X-feature/* または release-vX.X.X-fix/* 形式（既に feature/fix ブランチ上）:
新規ブランチは作成しない。現在のブランチのまま作業を続ける。
ケース 3: develop・master などその他のブランチ:
git checkout -b feature/bump-up-to-v<new-version>
Step 3: project.pbxproj を更新
MyApp.xcodeproj/project.pbxproj 内の MARKETING_VERSION をすべて新バージョンに更新する。
- 対象行:
MARKETING_VERSION = <old-version>;（Debug・Release 各 1 行、計 2 行） - 変更後:
MARKETING_VERSION = <new-version>;
注意: テストターゲットは変更しない。
更新後に確認する：
grep -n "MARKETING_VERSION" MyApp.xcodeproj/project.pbxproj
Step 4: コミット
コミットメッセージは必ず以下の形式を使用する：
Bump up v<new-version>
git add MyApp.xcodeproj/project.pbxproj
git commit -m "Bump up v<new-version>"
出力形式
完了後、以下を報告する：
- 作成したブランチ名
- 変更前 → 変更後のバージョン
- コミットハッシュ
注意事項
MARKETING_VERSION = 1.0;の行は変更しない（テストターゲット用）- 変更対象は必ず Debug・Release の 2 行
- コミットメッセージは
Bump up vX.X.X形式で統一
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.
- 11d ago First seen · 114 lines · 85 tokens per session scan A 62f4302bcc4b
ios-bump-version is a skill published in the GitHub repository CH3COOH/claude-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 85 tokens to every session and 1,098 once invoked, about $0.0004 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
apple-release-ops
The mechanics of shipping Apple apps. Use for ANY code signing error ("no signing certificate", "provisioning profile doesn't include...", "revoked certificate"), provisioning profiles, certificates, entitlements, capabilities, TestFlight (groups, expiry, feedback), App Store Connect, uploading builds, xcodebuild…
asc-build-lifecycle
Track build processing, find latest builds, and clean up old builds with asc. Use when managing build retention or waiting on processing.
ios-appstore-builder
Prepare, configure, and publish iOS apps to the Apple App Store. Covers certificates, provisioning profiles, TestFlight, App Store submission, and review guidelines.
axiom-shipping
Use when preparing ANY app for submission, handling App Store rejections, writing appeals, or managing App Store Connect. Covers submission checklists, rejection troubleshooting, metadata requirements, privacy manifests, age ratings, export compliance.
release-new-version
Use when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and publishing to GitHub (main repo, optionally the Xposed repo).
suede-play-release
Suede Labs Google Play delivery skill: ship an Android release end to end from the agent interface, without opening the Play Console. Set up credentials, upload an AAB, promote between tracks, stage or complete a rollout, push per-locale release notes, and prove against the Play Developer API what is actually live.…