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.
git 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/create-pr-from-staged-changes)<a href="https://agentmods.dev/commands/carloshpdoc/ios-workflow-claude/create-pr-from-staged-changes"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/create-pr-from-staged-changes.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.00848 |
| Opus 5 | $0.00000 | $0.00424 |
| Sonnet 5 | $0.00000 | $0.00170 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
create-pr-from-staged-changes 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 7d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request
Project context: Values in angle brackets below (e.g.
<scheme>,<JIRA_KEY>,<flag-key-enum>) are resolved at runtime — detect them from the project (xcodebuild -list -jsonfor the scheme,git/ghfor repo & owner, the branch name for the Jira key, a codebase search for flag/font files), or ask if they cannot be inferred. This plugin ships no per-project config.
You are helping to create a pull request following the iOS team's standard template.
Task
When the user asks to create a PR or open a pull request:
- Commit staged changes (if not already committed)
- Push to remote with
-u origin [branch-name] - Create PR using gh with the template below
PR Template
Use this exact template when creating the PR with gh pr create:
## Pull Request Checklist
- [ ] I tested my code (for bug/feature)
- [ ] Documents have been revised and added/updated if necessary (for bug/feature fixes)
- [ ] The build was run locally, and all changes were pushed
- [ ] Feature tested for accessibility
## What is the current behavior?
[Describe the current behavior or link to a relevant issue]
## What is the new behavior?
[Describe the behavior or changes being added by this PR]
## Have any third-party libraries been added or changed?
[Describe what the libraries are, or write "No"]
## Does this change involve any AB testing?
[If so, what is the experiment's name and the link to it in the console? If not, what is the justification for the absence?]
## Evidence
[Screenshots/videos of how the components/functionalities are changed or created]
## Other information
[Any other important information to this PR]
🤖 Generated with [Claude Code](https://claude.com/claude-code)
PR Title Format
Follow this pattern for the title:
[TYPE][<JIRA_KEY>-XXXX] Description
Where TYPE is one of: BUILD, CI, DOCS, FEATURE, FIX, PERF, REFACTOR, STYLE, TEST
PR Label
Every PR must have exactly one report label. Select based on the nature of the change:
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.
- 7d ago First seen · 99 lines · 0 tokens per session scan A 2d2618f184d9
create-pr-from-staged-changes 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 848 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.
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.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.