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-status)<a href="https://agentmods.dev/commands/carloshpdoc/ios-workflow-claude/apollo-status"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/apollo-status.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.00513 |
| Opus 5 | $0.00000 | $0.00257 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
apollo-status 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 8d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apollo Migration Status
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.
Show the current Apollo removal migration progress.
Steps
1. Read the Tracking File
Read docs/apollo-migration-status.md and parse the migration table.
2. Calculate Summary Statistics
Count repositories by status:
- Done: Fully migrated to GraphQLClientProtocol
- Deleted: Removed (no longer needed)
- In-Progress: Currently being worked on
- Todo: Not yet started
- Not-Needed: Already uses non-Apollo pattern or not a repository
3. Show Progress
Display:
## Apollo Migration Progress
| Status | Count | Percentage |
|-------------|-------|------------|
| Done | X | X% |
| Deleted | X | X% |
| In-Progress | X | X% |
| Todo | X | X% |
| Not-Needed | X | X% |
| **Total** | **X** | **100%** |
Progress bar: [=========>..........] X%
4. Show In-Progress Repos
If any repos are in-progress, list them with their owner:
### Currently In-Progress
| Repository | Owner | Tier |
|------------|-------|------|
| ... | ... | ... |
5. Recommend Next Repos
Suggest the next 5 repositories to tackle, prioritizing:
- Tier 1 (simplest) first
- Fewer consumers = easier migration
- Repos in
<scheme>/Repositories/before<scheme>/Modules/(more standardized)
### Recommended Next
| Repository | Tier | Consumers | Location |
|------------|------|-----------|----------|
| ... | ... | ... | ... |
6. Show Recently Completed
List the last 5 completed migrations with their PR links (if available).
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.
- 8d ago First seen · 69 lines · 0 tokens per session scan A c8f7904266b2
apollo-status 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 513 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
debug
Structured debugging with parallel investigation agents.
release
Generate changelog, bump version, and create git tag.
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/.
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/.