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/jpd44/mesh44-plugins/preflightnpx skills add jpd44/mesh44-plugins --skill preflightgit clone --depth 1 https://github.com/jpd44/mesh44-pluginsWhat 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.00043 | $0.01580 |
| Opus 5 | $0.00022 | $0.00790 |
| Sonnet 5 | $0.00009 | $0.00316 |
| Haiku 4.5 | $0.00004 | $0.00158 |
Grade A, and why
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 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/app-kit:preflight — verify auth and CLIs
Run all checks, collect failures, then print a single summary. Don't bail on the first failure — the user wants to fix everything in one pass.
Load config first
Before any check, read ~/.config/mesh44/config.json:
cat ~/.config/mesh44/config.json
If it doesn't exist, fail with this message and stop:
Missing
~/.config/mesh44/config.json. Copy<plugin>/config.json.exampleto that path and fill in your AWS management account ID, SSO start URL, GitHub org, and developer dir.
Extract these values for use throughout the checks:
aws.mgt_account_idaws.sso_start_urlaws.sso_region(defaultus-east-1)aws.sso_role_name(defaultAdministratorAccess)github.orgdeveloper_dir(anddeveloper_dir_symlinks[])
Expected facts (from config)
| Thing | Source |
|---|---|
| AWS mgt account ID | aws.mgt_account_id |
| AWS region | aws.default_region |
| SSO start URL | aws.sso_start_url |
| GitHub org | github.org |
| Node | 24.14.0 (per mise.toml; any 22+ is workable) |
Checks
Run these in parallel (one Bash call each) and capture exit codes + stdout/stderr.
0. Working directory — must be the Developer root
pwd
Pass if the resolved path matches developer_dir from config (after expanding $HOME / ~) or any entry in developer_dir_symlinks. Use readlink -f . if ambiguous.
The whole new-app flow assumes the new project goes into ./<app-name> from here. If pwd is anywhere else (e.g., inside an existing project, or under ~), fail with:
Run this from your Developer directory:
cd <developer_dir>then re-run.
(substitute the actual configured path).
A. Local CLIs present
command -v aws >/dev/null && aws --version
command -v gh >/dev/null && gh --version | head -1
command -v mise >/dev/null && mise --version
command -v node >/dev/null && node --version
command -v npm >/dev/null && npm --version
command -v git >/dev/null && git --version
command -v npx >/dev/null && npx --version
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 · 165 lines · 43 tokens per session scan A 8101e4a91df6
preflight is a skill published in the GitHub repository jpd44/mesh44-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,580 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…