Borrowing it
Nothing to install: this file belongs to baijum/ukulele-companion. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/baijum/ukulele-companion/main/.claude/commands/preflight.mdgit clone --depth 1 https://github.com/baijum/ukulele-companionWrote 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/baijum/ukulele-companion/preflight)<a href="https://agentmods.dev/commands/baijum/ukulele-companion/preflight"><img src="https://agentmods.dev/badge/commands/baijum/ukulele-companion/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/baijum/ukulele-companion/preflight"><img src="https://agentmods.dev/badge/commands/baijum/ukulele-companion/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.00011 | $0.00217 |
| Opus 5 | $0.00005 | $0.00109 |
| Sonnet 5 | $0.00002 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00022 |
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 9d 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
Run scripts/preflight.sh and report the outcome.
- Summarize the automated gate results (ktlint ratchet, shared KMP tests, Android unit tests, Android lint). If any gate failed, show the relevant error output and propose the fix — do not declare the change ready.
- Then walk through the manual checklist the script prints. For each item, state whether it's relevant to the current change (based on what files were touched) and, where you can, verify it from the code; flag anything that needs the user to check on a device/simulator (TalkBack/VoiceOver, themes, High-G/Low-G, left-handed mode).
- Remember iOS build + VoiceOver are not covered by this script — call that out explicitly if iOS code changed.
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.
- 9d ago First seen · 17 lines · 11 tokens per session scan A fa4ab286d0b2
preflight is a command published in the GitHub repository baijum/ukulele-companion (14 stars, last pushed 6d ago), licensed MIT. It adds 11 tokens to every session and 217 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-30.
Other commands, from other repositories
feature-test
Create all tests for an implemented feature - unit tests (ViewModel, UseCase, Repository), Compose UI tests, and E2E user flow tests.
feature-build-fix
Compile the feature, run all tests, and iteratively fix compilation errors and test failures until everything passes. Max 5 iterations.
feature-build
Build a complete mobile feature from description to running code with E2E tests. Orchestrates 6 phases - planning, implementation, testing, build-fix, quality gate, and verification. Auto-detects platform.
feature-verify
Run final verification - pass@k test metrics, coverage report, and sign-off. Confirms feature is production-ready.
test-feature
Generate comprehensive tests for a KMP feature.
feature-learn
View and manage patterns learned from feature builds. Shows extracted instincts, confidence scores, and feature completeness history.