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/fullstack-phoenix/saas_kit/command-palettenpx skills add fullstack-phoenix/saas_kit --skill command-palettegit clone --depth 1 https://github.com/fullstack-phoenix/saas_kitWhat 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.00045 | $0.01277 |
| Opus 5 | $0.00023 | $0.00639 |
| Sonnet 5 | $0.00009 | $0.00255 |
| Haiku 4.5 | $0.00005 | $0.00128 |
Grade A, and why
command-palette 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 2d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command Palette
Adds a keyboard-driven command palette to the app. Press Cmd+K (macOS) or
Ctrl+K (Windows/Linux) to open an overlay that searches routes and database
records, then jumps to the result. It ships as a live_rendered LiveView mounted
in the root layout, a CommandPalette search module with per-context scopes
(app, and admin when present), and a CommandPalette.Format protocol you
implement to make any schema searchable.
When to use
- The app has grown enough navigation that users want a fast keyboard shortcut to jump between pages.
- You want a single search box over both routes and records (users, posts, teams).
- Don't reach for it on a tiny one- or two-page app — a nav bar is enough.
Dependencies
- Requires: None.
- Recommended: None. Record search uses
Flop(Flop.validate_and_run/3), so schemas you want searchable must already be Flop-configured. Routes-only search needs nothing extra.
Install
mix saaskit.feature.install command_palette
No installer decisions. The task wires up the JS hook and hotkeys.js vendor file,
generates the CommandPalette modules, mounts the LiveView in the root layout, and
injects a search button after the theme toggle in the app (and admin) layouts.
What it generates
lib/my_app_web/command_palette/command_palette.ex—MyAppWeb.CommandPalette, the search entry point. Holds@possible_contexts,routes/1, andschemas/1.lib/my_app_web/command_palette/format.ex— theMyAppWeb.CommandPalette.Formatprotocol plus defaultimpls forMap(routes) andMyApp.Users.User.lib/my_app_web/command_palette/result.ex—Resultstruct wrapping each hit (:record,:type,:first_type,:index).lib/my_app_web/live/command_palette_live.ex— the palette LiveView.assets/js/hooks/command_palette.js+assets/vendor/hotkeys.js— the JS hook and key-binding library; wired intoassets/js/hooks/index.jsandapp.js.- Mounts
live_render(..., MyAppWeb.Live.CommandPaletteLive, ...)inlib/my_app_web/components/layouts/root.html.heexand adds the⌘Kbutton to theapp/adminlayouts. - Tests under
test/my_app_web/.
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.
- 2d ago First seen · 130 lines · 45 tokens per session scan A 844b4a0c8206
command-palette is a skill published in the GitHub repository fullstack-phoenix/saas_kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 1,277 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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.