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/request-review)<a href="https://agentmods.dev/commands/carloshpdoc/ios-workflow-claude/request-review"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/request-review.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.01223 |
| Opus 5 | $0.00000 | $0.00611 |
| Sonnet 5 | $0.00000 | $0.00245 |
| Haiku 4.5 | $0.00000 | $0.00122 |
Grade A, and why
request-review 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Request PR Review
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.
Send a message to the # Slack channel requesting a PR review.
Usage
/request-review <pr_number> [description]
Arguments:
pr_number- The PR number to request review fordescription(optional) - Brief description of the changes
Examples:
/request-review 4315
/request-review 4315 "Fix white button color in Edit Photos screen"
Instructions
When this skill is invoked:
-
Parse arguments from
$ARGUMENTS:- Extract the PR number (required)
- Extract optional description
-
Get PR details if no description provided:
- Run
gh pr view <pr_number> --json title,urlto get PR info - Use the PR title as the description
- Run
-
Detect the PR type by reading the prefix in the title (
[FIX],[FEATURE],[REFACTOR],[PERF],[BUILD],[CI],[DOCS],[STYLE],[TEST]):- This drives which playful opener to use (see "Tone & Templates" below)
- If the prefix is missing, fall back to the generic opener
-
Compose the message using the templates below. Rules that always apply:
- Tom descontraído, em português, curto e direto — sem
cc @... - O time é marcado inline dentro da frase, usando
<!subteam^S058UQVG6MA|frontend>(nunca comocc, nunca como footer) - Uma linha de chamada + título do PR em negrito + linha do link
- Nunca acrescentar nenhuma assinatura, footer, ou texto do tipo "enviado por", "via Claude", "generated with...". A mensagem termina no link.
- Tom descontraído, em português, curto e direto — sem
-
Send the message to # channel:
- Use
mcp__claude_ai_Slack__slack_send_message - Channel: # (ID: C04EL113PTK)
- Use
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 · 117 lines · 0 tokens per session scan A be2a14c4da0f
request-review 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,223 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
review
Multi-agent code review with parallel validation.
gentle-sdd-ff
Fast-forward all SDD planning phases — proposal through tasks.
sdd-explore
Explore and investigate an idea or feature — reads codebase and compares approaches.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.
init
Install the formatters this repository needs, with every command visible before it runs.