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/stacked-prs)<a href="https://agentmods.dev/commands/carloshpdoc/ios-workflow-claude/stacked-prs"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/stacked-prs/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/commands/carloshpdoc/ios-workflow-claude/stacked-prs"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/stacked-prs.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.00019 | $0.01422 |
| Opus 5 | $0.00010 | $0.00711 |
| Sonnet 5 | $0.00004 | $0.00284 |
| Haiku 4.5 | $0.00002 | $0.00142 |
Grade A, and why
stacked-prs 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 9d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
Stacked PRs Workflow
You are creating semantic commits and splitting them into stacked upstream PRs, each under 600 added lines.
Task
Split uncommitted changes into multiple branches with semantic commits, where each branch is based on the previous one, creating a chain of PRs.
Workflow
Step 1: Analyze Changes
- Run
git statusandgit diff --statto identify all changed/new files - Ask the user which files should be excluded from commits (e.g., unrelated docs, settings changes, storekit files)
- Count lines per file:
wc -l <file>for new files,git diff --stat <file>for modified files
Step 2: Plan the Split
Group files into logical commits, each under 600 added lines:
Suggested grouping order (adapt to the actual changes):
- Models/DTOs — domain models, response types, shared models
- Data layer — repositories, data sources, mappers, queries, mock data
- Presentation — view models, coordinators, factories, use cases, views
- Tests — test mocks, unit tests (split further if over 600 lines)
Present the plan to the user with line counts per group before proceeding.
Step 2.5: Select PR Label
Every PR must have exactly one report label. Select once for the entire chain (all PRs get the same label):
| Label | Use when |
|---|---|
report-feature |
New feature or functionality |
report-improvement-fix |
Bug fix or UX improvement (not a new feature) |
report-tech-improvement |
Tech debt, CI/CD, refactoring, code removal |
report-analytics-fix |
Analytics-related changes |
Auto-inference from TYPE:
- FEATURE →
report-feature - FIX →
report-improvement-fix - REFACTOR, BUILD, CI, PERF, STYLE, DOCS, TEST →
report-tech-improvement
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.
- 9d ago First seen · 160 lines · 19 tokens per session scan A 7a8f20c960fc
stacked-prs is a command published in the GitHub repository carloshpdoc/ios-workflow-claude (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,422 once invoked, about $0.0001 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 commands, from other repositories
speckit.companion.living-sync
Sync living specs from your current changes — group working-tree changes (uncommitted included) by capability and update every affected spec in one pass (opt-in, update-not-regenerate, never halts).
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
fest-commit
Commit changes with festival traceability metadata.
commit
Analyze git diffs or staged changes and generate conventional commit messages that explain WHY a change was made. Supports auto-detecting type and scope, intelligent file staging, and interactive overrides. Use when asked to "write a commit message", "generate a commit", "describe my changes", "commit this"…
release
Generate changelog, bump version, and create git tag.
commit
Based on the above changes, create a single git commit for the staged changes.