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/natsnpx skills add linuxfoundation/lfx-self-serve --skill natsgit clone --depth 1 https://github.com/linuxfoundation/lfx-self-serveWrote 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/skills/linuxfoundation/lfx-self-serve/nats)<a href="https://agentmods.dev/skills/linuxfoundation/lfx-self-serve/nats"><img src="https://agentmods.dev/badge/skills/linuxfoundation/lfx-self-serve/nats.svg" alt="Measured on agentmods" 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 | $0.00072 | $0.00627 |
| Opus 5 | $0.00036 | $0.00313 |
| Sonnet 5 | $0.00014 | $0.00125 |
| Haiku 4.5 | $0.00007 | $0.00063 |
Grade A, and why
nats 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 4d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self Serve NATS Skill
You are publishing, subscribing, or making NATS request/reply calls from the Self Serve Express BFF.
When to use
- A backend endpoint needs to look up a resource via NATS request/reply (e.g., project RPC for ID resolution).
- A backend service consumes a NATS subject (e.g., listening for indexer or persona updates).
- A new server-side code path needs to publish to NATS.
- Investigating "no responder" / timeout / connection errors in
nats.service.ts.
Workflow
- Re-read
docs/architecture/backend/nats-integration.md(the reference linked below). It documents the singleton connection, request/reply timeout defaults, project resolution, and the subject conventions Self Serve consumes. - Do not bypass
nats.service.ts— it is a protected file. Use the existing helper methods; add new methods through code-owner review. - Use the right subject vocabulary — subjects are owned by their producing service (per
/lfx-skills:lfx). Do not invent new subjects from Self Serve; coordinate with the owning service repo first. - Set explicit timeouts on request/reply calls. Failures must surface as
MicroserviceError(or equivalent) and route throughnext(error)— neverres.status(500).json(). - Log via the
loggerservice (notserverLogger). Uselogger.debugfor subject + reply tracing,logger.errorfor failed requests. - Mock mode — for local dev without the full platform stack, follow
docs/architecture/backend/nats-integration.mdand the mock-mode setup in/setup. Do not introduce ad-hoc mocks inside production code paths.
Reference
docs/architecture/backend/nats-integration.md— the canonical NATS architecture doc. Treat this as the source of truth; do not maintain a separate copy under this skill.
Scope boundaries
- This skill does NOT cover the platform NATS deployment (routes to
lfx-v2-helm). - It does NOT cover indexer or FGA-sync subject contracts (routes to
lfx-v2-indexer-serviceandlfx-v2-fga-syncvia/lfx-skills:lfx). - It does NOT cover the upstream auth or persona NATS contracts (route to
lfx-v2-auth-service/lfx-v2-persona-service).
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.
- 4d ago First seen · 36 lines · 72 tokens per session scan A 28df3c5a2767
nats is a skill published in the GitHub repository linuxfoundation/lfx-self-serve (11 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 627 once invoked, about $0.0004 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…