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.
git clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWrote 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/vmobifystudio/app-dev-team/app-preflight)<a href="https://agentmods.dev/commands/vmobifystudio/app-dev-team/app-preflight"><img src="https://agentmods.dev/badge/commands/vmobifystudio/app-dev-team/app-preflight/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/vmobifystudio/app-dev-team/app-preflight"><img src="https://agentmods.dev/badge/commands/vmobifystudio/app-dev-team/app-preflight.svg" alt="Reviewed on agentmods" width="80" 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.00181 |
| Opus 5.5 | $0.00000 | $0.00072 |
| Sonnet 5.5 | $0.00000 | $0.00036 |
| Haiku 4.5 | $0.00000 | $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 1mo 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.
- 1mo 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 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 181 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
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
ux-grill
Use when a running web app's UX has to be audited reproducibly rather than by feel — a deterministic mechanical pass over routes and viewports (axe, target size, horizontal overflow, page title, scripted journeys) followed by a screenshot-grounded interrogation of the operator, journey by journey, with two persona…
write-executable-plan
Use when you have a PRD or design spec and need a bite-sized, executable implementation plan that any agent can follow without re-deriving structure. Produces docs/plans/YYYY-MM-DD- .md with per-task Files block, complete code per step (no placeholders), and exact verification commands. Rejects "TBD", "TODO", "add…
go
Approve session plan and begin wave execution.
harness-audit
Run the harness audit and report the rubric score for this repository.
factory-ticket
Implement exactly one already-claimed Linear ticket in the current worktree.