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/open-pr)<a href="https://agentmods.dev/commands/carloshpdoc/ios-workflow-claude/open-pr"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/open-pr.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.02624 |
| Opus 5 | $0.00000 | $0.01312 |
| Sonnet 5 | $0.00000 | $0.00525 |
| Haiku 4.5 | $0.00000 | $0.00262 |
Grade A, and why
open-pr 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 — 238 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.
Create a pull request for the current branch following the the team's standard PR template.
$ARGUMENTS (optional): space-separated options. All are optional and can be combined in any order.
| Argument | Description | Default |
|---|---|---|
--base <branch> |
Base branch for the PR | dev |
--draft |
Create as draft PR | off |
--reviewer <user> |
Add reviewer(s). Can repeat: --reviewer user1 --reviewer user2 |
none |
--label <name> |
Add label(s). Can repeat: --label bug --label urgent |
none |
For convenience, a bare value (no -- prefix) is treated as --base <value>.
Examples:
/open-pr- PR todev/open-pr main- PR tomain(shorthand for--base main)/open-pr --base feature/<JIRA_KEY>-XXXX-some-feature- PR to another feature branch/open-pr --draft- Draft PR todev/open-pr --base feature/<JIRA_KEY>-XXXX --draft --reviewer jvlcapi- Draft PR to a feature branch with reviewer/open-pr --label bug --reviewer jvlcapi --reviewer other-dev- PR todevwith label and two reviewers
Steps
1. Parse Arguments
Parse $ARGUMENTS to extract:
- --base : the target base branch, or
devif not provided. A bare value (no--prefix) is also treated as the base branch for convenience (e.g.,mainis equivalent to--base main) - --draft: if present, add
--draftflag togh pr create - --reviewer : collect all
--reviewervalues, add each as--reviewer <user>togh pr create - --label : collect all
--labelvalues, add each as--label <name>togh pr create
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 · 238 lines · 0 tokens per session scan A 614741c472b8
open-pr 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 2,624 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
merge
Finish a PR properly: every check green, every review addressed — human and bot — then merge and clean up.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
check
Run the formatting gate over the changed files, as a commit or CI would.