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/apollo-check)<a href="https://agentmods.dev/commands/carloshpdoc/ios-workflow-claude/apollo-check"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/apollo-check.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.02118 |
| Opus 5 | $0.00000 | $0.01059 |
| Sonnet 5 | $0.00000 | $0.00424 |
| Haiku 4.5 | $0.00000 | $0.00212 |
Grade A, and why
apollo-check 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apollo Repository Investigation
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.
Investigate the Apollo repository $ARGUMENTS and produce a detailed investigation for migration.
Output: This command creates an investigation file at docs/apollo-removal/issues/$ARGUMENTS.md that serves as the "issue" for this migration. The /apollo-migrate command will read this investigation before executing the fixed migration steps.
Steps
1. Find All Related Files
Search for all files related to this repository:
Glob: **/$ARGUMENTS*
Glob: **/Network$ARGUMENTS*
Grep: "$ARGUMENTS" in *.swift files
Look specifically for:
.graphqlfile (query definition) - usually in<scheme>/Repositories/<Name>/or<scheme>/Modules/<Feature>/Repository/.graphql.swiftfile (Apollo-generated types) - usually in<scheme>/Services/Apollo/API/Network*Repository.swift(old implementation using Apollo)- Any existing new-pattern files (
*GraphQLDataSource.swift,*Query.swift, etc.) - Fragment extension files (
*+Fragments.swift)
2. Read the Implementation
Read the old Network*Repository.swift file to understand:
- What queries/mutations does it perform?
- What Apollo types does it use?
- What protocol does it conform to?
- What domain models does it return?
- What cache policies does it use?
Read the .graphql file to get the query string.
Read the .graphql.swift file to understand nullability of fields (.nonNull vs optional).
3. Find All Consumers
Search for all files that import or use this repository:
Grep: protocol name (e.g., "<Name>RepositoryProtocol" or "<Name>Repository")
Grep: class instantiation (e.g., "Network<Name>Repository(")
Grep: factory usage if exists
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 · 213 lines · 0 tokens per session scan A 686260e25e7f
apollo-check 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,118 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
mobile-app-testing
Read .cursor/playwright-skills/mobile-app-testing/SKILL.md and follow its instructions exactly. Treat that file's body as your operating instructions for this task. Template files to install live in .cursor/playwright-skills/mobile-app-testing/templates/.
debug
Structured debugging with parallel investigation agents.
review
Multi-agent code review with parallel validation.
prompt-pilot
Rewrite a rough prompt into a precise, context-enriched prompt (read-only — never implements the task).
e2e-dashboard
Read .cursor/playwright-skills/e2e-dashboard/SKILL.md and follow its instructions exactly. Treat that file's body as your operating instructions for this task. Template files to install live in .cursor/playwright-skills/e2e-dashboard/templates/.
aw-upgrade
Upgrade gh-aw extension, recompile and validate all workflows, and open a PR with changes.