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 commands/carloshpdoc/ios-workflow-claude/bumpgit clone --depth 1 https://github.com/carloshpdoc/ios-workflow-claudeWrote 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/commands/carloshpdoc/ios-workflow-claude/bump)<a href="https://agentmods.dev/commands/carloshpdoc/ios-workflow-claude/bump"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/bump.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.1 | $0.00000 | $0.01299 |
| Opus 5 | $0.00000 | $0.00649 |
| Sonnet 5 | $0.00000 | $0.00260 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
bump 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 6d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump Version
Bump the app version or build number across all targets in the current project.
$ARGUMENTS: the bump type. If empty, defaults to build.
| Argument | Description | Example |
|---|---|---|
build |
Increment build number only | 1 -> 2 |
patch |
Bump patch version, increment build | 1.0.0 -> 1.0.1 |
minor |
Bump minor version, increment build | 1.0.0 -> 1.1.0 |
major |
Bump major version, increment build | 1.0.0 -> 2.0.0 |
Examples:
/bump- Increment build number (default)/bump build- Increment build number/bump patch- Bump patch version/bump minor- Bump minor version/bump major- Bump major version
Steps
1. Parse Arguments
Read $ARGUMENTS and determine the bump type:
- If empty or
build-> bump build number only - If
patch-> bump patch, increment build - If
minor-> bump minor, increment build - If
major-> bump major, increment build - If anything else -> tell the user the valid options and stop
2. Detect Project Type
Check what version source exists in the current working directory:
Option A — XcodeGen (project.yml):
Look for project.yml in the project root. If found, this is the source of truth. Extract the current MARKETING_VERSION and CURRENT_PROJECT_VERSION values from it.
Option B — Native Xcode (.pbxproj):
If no project.yml exists, find the .pbxproj file (typically at *.xcodeproj/project.pbxproj). Extract the current MARKETING_VERSION and CURRENT_PROJECT_VERSION values from it.
If neither exists, tell the user no version source was found and stop.
3. Read Current Versions
Extract the current values:
- MARKETING_VERSION (e.g.,
1.0.0) — the user-facing version - CURRENT_PROJECT_VERSION (e.g.,
3) — the build number
If multiple different values exist across targets (e.g., some targets at build 3, others at build 1), warn the user and show the discrepancies. Use the highest value as the baseline for bumping, and the bump will unify all targets to the same new value.
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.
- 6d ago First seen · 119 lines · 0 tokens per session scan A 33d2a1500231
bump is a command published in the GitHub repository carloshpdoc/ios-workflow-claude (7 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,299 tokens. 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 commands, from other repositories
release
Generate changelog, bump version, and create git tag.
release
Bump version, commit, push, mirror to ai-skills, and update local plugin.
cancel-ship
Cancel active ship pipeline.
aw-upgrade
Upgrade gh-aw extension, recompile and validate all workflows, and open a PR with changes.
aw-merge
Merge develop branch to main with PR, CI check, and squash merge.
release
You are performing a release for the mindkeg-mcp project. The user will provide the version as $ARGUMENTS (e.g., "0.2.0" or "patch" or "minor" or "major").