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 skills/vmobifystudio/app-dev-team/context-preflightnpx skills add vmobifystudio/app-dev-team --skill context-preflightgit 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/skills/vmobifystudio/app-dev-team/context-preflight)<a href="https://agentmods.dev/skills/vmobifystudio/app-dev-team/context-preflight"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/context-preflight.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.00032 | $0.00376 |
| Opus 5 | $0.00016 | $0.00188 |
| Sonnet 5 | $0.00006 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
context-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 today.
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
Context preflight
Use before implementation, review, migration, release, or any command that can change files. The purpose is not to create more ceremony; it is to prevent an agent from acting on stale context.
Procedure
- Run
node "${CLAUDE_PLUGIN_ROOT}/scripts/context-preflight.mjs" <project-root> [--ticket ID]. - Read the reported branch, dirty-tree, active-worktree, ticket, and required-document findings.
- Read the ticket, its dependency ancestors, the architecture/engineering-principles docs, the Git strategy, and the latest relevant decision or follow-up before editing.
- If the result is
CANNOT EVALUATE, stop. Do not convert missing context into an assumption. - Record assumptions and the next action in the ticket's daily evidence file.
Operating rules
- A dirty tree belongs to somebody until proven otherwise. Preserve it and ask before overlapping it.
- The current branch and worktree are facts, not suggestions. Never work on
mainwhen the task writes. - A ticket is not ready because it is assigned; its dependencies must be merged and its acceptance criteria must be discoverable.
- Read the latest decision and unresolved follow-up before reopening a settled thread.
- Report facts, assumptions, decisions, and unknowns separately. Never present reasoning as execution.
Output
Return: PREFLIGHT: CLEAR | BLOCKED | CANNOT EVALUATE, repository identity, branch/worktree state,
ticket/dependency state, documents read, assumptions, and the next safe action. Keep the report short;
the evidence files carry detail.
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.
- today First seen · 34 lines · 32 tokens per session scan A 46894320055f
context-preflight is a skill published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 24d ago), licensed MIT. It adds 32 tokens to every session and 376 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
execute-task
Implement one task (or a cohesion bundle) from a signed-off spec (Ready or Active): recompute the execution freshness gate, write the verifying test first, implement to green, run the project's full CI with adaptive retry, converge via the configured reviewsequence (default /polish --nested), then open a draft PR…
builder
Detect a project's stack and recommend or apply the universal mechanical quality guards from planwright's core catalog (formatter, linters, type-checker, test runner, secret scan, commit hooks, CI gate), plus the growable breadth dimensions. Escalates stake-bearing decisions (auth, data modeling, security posture…
spec-walkthrough
Render a spec bundle (or a chosen slice) into a plain-language, didactic comprehension artifact a human reads and judges for themselves: an unaided cold read before kickoff, re-orientation mid-execution, or onboarding to a finished or abandoned spec. Standalone and strictly read-only: it renders any status, never…
drain
Run the on-demand drain pass over every spec bundle's Gate deferral entries: evaluate structured GATE(when:) conditions, surface date and free-text gates, report malformed ones, inventory each live bundle's [manual] test-spec entries, and surface the observations log's unmined state. Read-only; nothing is…
orchestrate
Advance one planwright spec by one step: pick the next ready unit critical-path-first (or a cohesion bundle), run the freshness gate, record the dispatch under the per-spec lock, and dispatch /execute-task via the backend. A stateless, disposable control tower; a reconcile sweep rebuilds from disk. Never merges, marks…
spec-kickoff
Walk a spec bundle section by section to mutual understanding, producing the signed-off kickoff brief downstream skills execute from. On sign-off: runs the Discovery-Rigor lens pass, flips Draft to Ready, records the sign-off record (anchor last), commits, pushes, opens a draft PR, then on clean completion marks the…