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/vmobifystudio/app-dev-team/app-shipgit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWhat 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.00021 | $0.05551 |
| Opus 5 | $0.00010 | $0.02776 |
| Sonnet 5 | $0.00004 | $0.01110 |
| Haiku 4.5 | $0.00002 | $0.00555 |
Grade A, and why
app-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 yesterday.
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 — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/app-ship — Cut a release
Version (optional, otherwise release-manager picks): $ARGUMENTS
Steps
-
Bind the artifact, then run every mechanical precondition as ONE command.
First bind what you are about to ship to the commit that passed. Everything else here reasons about a COMMIT; until the binary is bound to it, "readiness: PASS" is a true statement about source and silent about the file you hand to a store:
node "${CLAUDE_PLUGIN_ROOT}/scripts/release-candidate.mjs" record \ --artifact <path to the built .ipa/.aab> --platform ios|android --variant release \ --by release-managerThis step stays explicit because only you know the artifact path — guessing it would be inventing the subject of the whole release. A build from a dirty tree records as such and reads STALE forever after; that is not a bug to work around.
Then:
node "${CLAUDE_PLUGIN_ROOT}/scripts/orchestrator.mjs" shipThat runs the board doctor, the ONE readiness reducer (which now includes the artifact you just bound) and
ship-gate.sh, in order, worst answer wins. They were three separate steps each ending in "read the exit code"; the discipline of running all three, every time, is exactly what a 328-line file erodes.- Exit
0→ continue to the runtime gate below. - Exit
1→ do not release. It names which precondition. STALE is not a failure — nothing says the product is broken, it says nobody checked THIS candidate. Re-run the gates it names, or rebuild and re-record. - Exit
2→ CANNOT EVALUATE, also not a pass. A gate has never run, or no artifact was recorded, so what would be uploaded is UNKNOWN.
Confirm the gate results still describe this candidate rather than last Tuesday's:
node "${CLAUDE_PLUGIN_ROOT}/scripts/evidence-check.mjs" \ --result docs/team/journey-result.json --head "$(git rev-parse HEAD)"Every gate answers at a moment and then stops thinking.
journey-gatesays PASS, three commits land, and the PASS sits there green describing a candidate that no longer exists. Nobody lied; the verdict outlived its subject. Exit1→ re-run the gate rather than reasoning about how little changed. - Exit
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.
- yesterday First seen · 330 lines · 21 tokens per session scan A 4113b4dfa623
app-ship is a command published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 22d ago), licensed MIT. It adds 21 tokens to every session and 5,551 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
analyze-cluster-postmortem
Postmortem analysis of cluster failures → OPTIMIZE PROMPTS to work for EVERY use case.
factory-ticket
Implement exactly one already-claimed Linear ticket in the current worktree.
factory-friction
File harness friction observed in an interactive session — capture only, never implement.
factory-next
Recommend and optionally run the next factory stage for this repo.
factory-report
Linear status report across configured repos — queue depth, triage backlog, ready-to-dispatch, blocked/held.
commit-all
Stage and commit all current changes with a single message. Auto Git Push will pick up and push to origin within 30s.