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/adilkalam/orca/expogit clone --depth 1 https://github.com/adilkalam/orcaWrote 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/adilkalam/orca/expo)<a href="https://agentmods.dev/commands/adilkalam/orca/expo"><img src="https://agentmods.dev/badge/commands/adilkalam/orca/expo.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 | $0.00022 | $0.06698 |
| Opus 5 | $0.00011 | $0.03349 |
| Sonnet 5 | $0.00004 | $0.01340 |
| Haiku 4.5 | $0.00002 | $0.00670 |
Grade A, and why
expo 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 3d 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 — 757 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STOP - DELEGATION ONLY
Before you do ANYTHING else, read this.
This slash command EXISTS to delegate work to agents. Not to do work directly.
NEVER acceptable:
- "This is simple, I'll just do it directly"
- "Let me quickly fix this"
- "I can handle this without agents"
- Using Edit/Write tools to make changes yourself
ALWAYS required:
- Parse the arguments
- Determine routing (--tweak, default, --complex)
- Spawn specialists single-level via the
Agenttool (you are the orchestrator, in the main thread — no orchestrator subagent; OS 7.1)
Even --tweak delegates to a builder. It skips gates, not agents.
If you are about to Edit/Write, STOP. Delegate instead.
/expo - Expo Lane Orchestrator (OS 7.1)
Use this command for Expo/React Native mobile work.
Usage
/expo "add pull-to-refresh to product list" # Default: light path + design gates
/expo --tweak "fix button spacing" # Fast: light path, no gates
/expo --complex "multi-screen auth flow" # Full: architect + builder + all gates
/expo "implement requirement 2025-11-25-auth" # Full path with spec
CRITICAL ROLE BOUNDARY
YOU ARE AN ORCHESTRATOR. YOU NEVER WRITE CODE.
- DO NOT use Edit/Write tools
- DO NOT bypass the agent system
- DELEGATE via the
Agenttool only (single-level, from the main thread) - Update phase_state.json to track progress
- Resume from interruptions without abandoning pipeline
0. Parse Arguments & Detect Mode
Check for flags:
$ARGUMENTS contains "--light" → Section 2.1 (Light Orchestrator, NO confirmation)
$ARGUMENTS contains "--tweak" → Section 2.2 (Builder Direct, NO confirmation)
$ARGUMENTS contains "--complex" → Section 3 (Full Pipeline with confirmation)
No flag → Section 3 (Light Orchestrator WITH confirmation)
0.1 Recording Context (OS 7.1)
Session activity is captured automatically by orca-record hooks. Before delegating to agents, inject prior session context for continuity.
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.
- 3d ago First seen · 757 lines · 22 tokens per session scan A 964ce4798452
expo is a command published in the GitHub repository adilkalam/orca (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 6,698 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
review-android
Guided Android code review workflow through context gathering, Android-specific review, and output.
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.
build-verify
Run the full build / test / analyze / format verification pass for this Flutter app.
create-pr-from-staged-changes
You are helping to create a pull request following the iOS team's standard template.
apollo-status
Show the current Apollo removal migration progress.
ios-privacy
Prepare privacy labels, permissions, policy links, and data-use truth for iOS release.