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/drawernpx skills add linuxfoundation/lfx-self-serve --skill drawergit 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.00070 | $0.00685 |
| Opus 5 | $0.00035 | $0.00342 |
| Sonnet 5 | $0.00014 | $0.00137 |
| Haiku 4.5 | $0.00007 | $0.00068 |
Grade A, and why
drawer 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self Serve Drawer Skill
You are building or modifying a Self Serve drawer. Drawers are slide-in detail panels built on p-drawer with strict conventions for visibility, lazy data, chart integration, and responsive sizing.
When to use
- A new module asks for a "drawer", "side panel", or "detail panel" that slides in.
- An existing drawer needs new sections, charts, or async data.
- A list-row click needs to open detail content without a route change.
- A component currently uses
DialogService.openfor content that should slide rather than modal-pop.
If the work is a modal dialog (not a slide-in), this skill does not apply.
Workflow
- Re-read
docs/architecture/frontend/drawer-pattern.md(the reference linked below). The full pattern — visibility model, lazy load viatoObservable(visible).pipe(skip(1), switchMap(...)),forkJoinfor parallel calls, chartcomputed()signals, responsive width — is the source of truth. - Check what exists — read at least one current drawer in the touched module before generating new code to match the team's current shape.
- Place files following the component placement table in
docs/architecture/frontend/component-architecture.md(and the high-level decision tree indocs/architecture/placement.md). - Generate three files (
.component.ts,.component.html,.component.scss) with the LFX license header on each. Follow the 11-section class structure from.claude/rules/component-organization.md. - Wire visibility with
model<boolean>(false)— two-way[(visible)]from the parent. - Lazy-load data on open —
toSignalovertoObservable(this.visible).pipe(skip(1), switchMap(...)); resetdrawerLoadingtofalseon close.forkJoinfor parallel calls. - Use the standard width chain —
xl:w-[45%] lg:w-[55%] md:w-[70%] sm:w-[90%] w-full. - Run
yarn formatafter writing files. Report what was changed.
Reference
docs/architecture/frontend/drawer-pattern.md— the canonical drawer architecture doc. Treat this as the source of truth; do not maintain a separate copy under this skill.
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 · 40 lines · 70 tokens per session scan A 22218019f6fe
drawer is a skill published in the GitHub repository linuxfoundation/lfx-self-serve (11 stars, last pushed 3d ago), licensed MIT. It adds 70 tokens to every session and 685 once invoked, about $0.0003 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…