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/guillemroca/agent-skills-android/shipgit clone --depth 1 https://github.com/GuillemRoca/agent-skills-androidWrote 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/guillemroca/agent-skills-android/ship)<a href="https://agentmods.dev/commands/guillemroca/agent-skills-android/ship"><img src="https://agentmods.dev/badge/commands/guillemroca/agent-skills-android/ship.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.00029 | $0.02028 |
| Opus 5 | $0.00015 | $0.01014 |
| Sonnet 5 | $0.00006 | $0.00406 |
| Haiku 4.5 | $0.00003 | $0.00203 |
Grade A, and why
ship 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 4d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ship — Shipping and Launch (Android)
Invoke the shipping-and-launch skill from skills/shipping-and-launch/SKILL.md.
/ship is a fan-out orchestrator. It runs three specialist personas in parallel against the current change, then merges their reports into a single go/no-go decision with a rollback plan and staged Play Store rollout. The personas operate independently — no shared state, no ordering — which is what makes parallel execution safe and useful here.
Phase A — Parallel fan-out
Spawn three subagents concurrently using the Agent tool. Issue all three Agent tool calls in a single assistant turn so they execute in parallel — sequential calls defeat the purpose of this command.
In Claude Code, each call passes subagent_type matching the persona's name field:
code-reviewer— Run a five-axis review (correctness, readability, architecture, security, performance) on the staged changes or recent commits. Output the standard review template.security-auditor— Run a vulnerability and threat-model pass against OWASP Mobile Top 10. Check secrets, exported components, deep links, Network Security Config, cert pinning, dependency CVEs, ProGuard/R8 config. Output the standard audit report.test-engineer— Analyze test coverage for the change. Identify gaps in happy path, edge cases, error paths, and concurrency (coroutines, Flow). Cover ViewModel state transitions, Repository boundaries, Room DAO behavior, and Compose UI states. Output the standard coverage analysis.
In other harnesses without an Agent tool, invoke each persona's system prompt sequentially and treat their outputs as if returned in parallel — the merge phase still works.
Constraints (from Claude Code's subagent model):
- Subagents cannot spawn other subagents — do not let one persona delegate to another.
- Each subagent gets its own context window and returns only its report to this main session.
- If you need teammates that talk to each other instead of just reporting back, use Claude Code Agent Teams and reference these personas as teammate types (see
references/orchestration-patterns.md).
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.
- 4d ago First seen · 149 lines · 29 tokens per session scan A 533281def790
ship is a command published in the GitHub repository GuillemRoca/agent-skills-android (2 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 2,028 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
toh-mobile
Turn the current web app into a mobile app — PWA (default) or native store build (Capacitor).
al-agent-instructions-create
Generate optimized natural language instructions for Business Central agents (Designer or SDK). Follows Responsibilities-Guidelines-Instructions framework. Use when writing agent instructions or creating InstructionsV1.txt.
create-activity
Generate a Jetpack Compose screen with proper architecture.
create-view
Generate a SwiftUI view with proper architecture and best practices.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
fdk-migrate
Migrate a legacy Freshworks app from platform-version 2.3 (2.x), FDK 9.x, and Node 18 to Platform 3.0 with FDK 10.0.1 and Node 24.11.0. Transforms manifest, request templates, Crayons UI, and validates on the new toolchain. Does not install fdk/Node—use fw-setup (or prompt user to add it) per SKILL.md.