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.
npx agentmods add commands/carloshpdoc/ios-workflow-claude/apollo-migrategit 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-migrate)<a href="https://agentmods.dev/commands/carloshpdoc/ios-workflow-claude/apollo-migrate"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/apollo-migrate.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.02832 |
| Opus 5 | $0.00000 | $0.01416 |
| Sonnet 5 | $0.00000 | $0.00566 |
| Haiku 4.5 | $0.00000 | $0.00283 |
Grade A, and why
apollo-migrate 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 6d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apollo Repository Migration
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.
Migrate the Apollo repository $ARGUMENTS to the new GraphQLClientProtocol pattern.
Pre-Migration: Read the Investigation
MANDATORY: Before writing any code, read the investigation file:
docs/apollo-removal/issues/$ARGUMENTS.md
If the investigation file does NOT exist, tell the user to run /apollo-check $ARGUMENTS first and stop. Do not proceed without an investigation.
If the investigation file exists, read it completely. It contains:
- The design decisions already made (pattern, fragment handling, PR splitting)
- The exact files to create, modify, and delete
- The consumers to update
- The tests to write
- Any risks or special considerations
Follow the investigation. The migration steps are always the same (see CLAUDE.md). What changes per repo is the target files and consumers identified in the investigation. If you need to deviate from it, note the deviation and the reason — you will need to explain this in the report.
Reference
Read docs/apollo-migration-guide.md for the full migration guide.
Gold standard reference files (read before writing code):
<scheme>/Repositories/<ReferenceRepo>/Queries/<ReferenceRepo>Query.swift<scheme>/Repositories/<ReferenceRepo>/<ReferenceRepo>GraphQLDataSource.swift<scheme>/Repositories/<ReferenceRepo>/Models/<ReferenceRepo>GraphQLResponse.swift<scheme>/Repositories/<ReferenceRepo>/<ReferenceRepo>ResponseMapper.swift<scheme>/Repositories/<ReferenceRepo>/<ReferenceRepo>Repository.swift<scheme>/Repositories/<ReferenceRepo>/<ReferenceRepo>RepositoryFactory.swift
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.
- 6d ago First seen · 298 lines · 0 tokens per session scan A 7405f489887c
apollo-migrate 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,832 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
test-integration
Write integration tests for component boundaries.
composite-actions
Generate, review, secure, and test composite GitHub Actions following best practices — full repo scaffold, interview-driven generation, PR creation on existing repos, SHA pinning, secrets-as-inputs, job summaries, and actionlint validation.
github-actions
Design, review, secure, and debug GitHub Actions workflows — reusable workflows, OIDC federation, SHA pinning, token scoping, promotion orchestration, and CI failure diagnosis.
fluxcd
FluxCD entry point — routes to the right workflow based on what you need. Live cluster issue → structured 5-workflow debug trace. Repo health check → 6-phase audit (discovery, validation, API compliance, best practices, security). Helm chart review → helmchart. Starts by asking one question to confirm the right mode.
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.
newpkg
Generate new package with Nx.