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/linuxfoundation/lfx-self-serve/preflightnpx skills add linuxfoundation/lfx-self-serve --skill preflightgit clone --depth 1 https://github.com/linuxfoundation/lfx-self-serveWhat 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.00095 | $0.01534 |
| Opus 5 | $0.00048 | $0.00767 |
| Sonnet 5 | $0.00019 | $0.00307 |
| Haiku 4.5 | $0.00010 | $0.00153 |
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Submission Preflight Check
You are running the mechanical pre-PR pipeline before the contributor submits a pull request. Every check here is shell-driven or hook-driven, no judgment calls. Convention and pattern audits live in docs/reviews/frontend-checklist.md (sections 1-14) and run via the post-commit reviewer trio (see .claude/rules/skill-guidance.md for canonical post-commit reviewer-trio launch instructions).
Run each check in order, report results clearly, and help fix any issues found.
Check 0: Working Tree Status
Before running any validation, check the state of the working tree:
git status
git diff --stat origin/main...HEAD
git log --format="%h %s%n%b" origin/main...HEAD
Evaluate:
- Uncommitted changes? — Ask the contributor: commit now or stash?
- No commits ahead of main? — The branch has nothing to validate. Ask if they're on the right branch.
- Commit messages missing a ticket reference? — Flag commits that don't include
LFXV2-XXX(JIRA),#XXX(GitHub Issue), or the fully-qualifiedorg/repo#XXXform (e.g.linuxfoundation/lfx-self-serve#1331) in subject or body. See.claude/rules/commit-workflow.md§ Ticket Tracking. - Commits missing
--signoff? — Flag any commits withoutSigned-off-by:lines (visible in the full commit body above).
Resolve any issues before proceeding to the checks below.
Check 1: License Headers
./check-headers.sh
Every source file (.ts, .html, .scss) must have the license header:
- TypeScript/SCSS:
// Copyright The Linux Foundation and each contributor to LFX.+// SPDX-License-Identifier: MIT - HTML:
<!-- Copyright The Linux Foundation and each contributor to LFX. -->+<!-- SPDX-License-Identifier: MIT -->
If any files are missing headers, add them.
Check 2: Formatting
yarn format
This applies Prettier formatting with Tailwind class sorting. It modifies files in place.
Why format before lint: Prettier auto-fixes whitespace, import ordering, and line-length issues that would otherwise appear as lint errors. Running format first eliminates noise from the lint step.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 183 lines · 95 tokens per session scan A 4b5a24f341ea
preflight is a skill published in the GitHub repository linuxfoundation/lfx-self-serve (11 stars, last pushed 3d ago), licensed MIT. It adds 95 tokens to every session and 1,534 once invoked, about $0.0005 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-30.
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.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…