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-preflightgit 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.00015 | $0.00181 |
| Opus 5 | $0.00008 | $0.00090 |
| Sonnet 5 | $0.00003 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
app-preflight 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 2d 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.
What it actually says
/app-preflight — establish context before acting
Run context-preflight.mjs first. Then run dependency-check.mjs when dependency manifests exist,
version-consistency-check.mjs when a release record exists, and policy-check.mjs when the project
has .studio-policy.json. Exit 1 is a blocker; exit 2 is CANNOT EVALUATE, never a pass.
Read the reported branch, ticket, dependency ancestors, architecture, engineering principles, Git strategy, latest decisions, and unresolved follow-ups before making changes. Return facts, assumptions, unknowns, and the next safe action separately.
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.
- 2d ago First seen · 16 lines · 0 tokens per session scan A 77963d64abf5
app-preflight is a command published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 22d ago), licensed MIT. It adds 15 tokens to every session and 181 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
release
Prepare, cut, and verify a warren release — tracker audits, version bump, CHANGELOG curation, ROADMAP update, push, then watch the pipeline through to published artifacts.
factory-merge
Review open PRs thoroughly, fix what's fixable, merge what's good.
factory-retro
Find what is repeatedly wasting the factory's time and fix the harness, not the symptom.
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.