Borrowing it
Nothing to install: this file belongs to linuxfoundation/lfx-self-serve. 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/linuxfoundation/lfx-self-serve/main/.claude/skills/setup/SKILL.mdgit 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/setup)<a href="https://agentmods.dev/skills/linuxfoundation/lfx-self-serve/setup"><img src="https://agentmods.dev/badge/skills/linuxfoundation/lfx-self-serve/setup/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/skills/linuxfoundation/lfx-self-serve/setup"><img src="https://agentmods.dev/badge/skills/linuxfoundation/lfx-self-serve/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 48 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 62 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Tool Misuse · line 115 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
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.00044 | $0.01365 |
| Opus 5.5 | $0.00018 | $0.00546 |
| Sonnet 5.5 | $0.00009 | $0.00273 |
| Haiku 4.5 | $0.00004 | $0.00136 |
Grade A, and why
setup 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 1mo 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Environment Setup Guide
You are helping a contributor set up the LFX One development environment from scratch. Walk through each step interactively, verifying success before moving on.
Step 1: Prerequisites
Check that the following are installed:
- Node.js 22.13+ (or 23.4+) — Run
node --versionto verify. If missing, instruct them to install via nvm or nodejs.org. - Yarn v4.9.2+ — Run
yarn --versionto verify. This project uses Yarn Berry (Corepack). If missing:corepack enable && corepack prepare [email protected] --activate. - Git — Run
git --versionto verify.
Docker is NOT required for local development. All services point to the shared dev environment — no local databases, message brokers, or infrastructure to run.
Step 2: Clone the Repository
If not already cloned:
git clone <repository-url>
cd lfx-self-serve
If already in the repo, confirm the working directory:
pwd
git remote -v
Step 3: Environment Variables
The project requires environment variables to connect to backend services. All values are available through 1Password.
-
Copy the env template:
cp apps/lfx-one/.env.example apps/lfx-one/.env -
Get credentials from 1Password:
- Access the LFX One Dev Environment vault in 1Password
- Copy all required values into
apps/lfx-one/.env - The
.env.examplefile documents every variable and its purpose — use it as your reference - If you don't have 1Password access, contact a code owner on Slack for help
-
Validate critical env vars are populated:
missing=() for key in PCC_AUTH0_CLIENT_ID PCC_AUTH0_CLIENT_SECRET PCC_AUTH0_ISSUER_BASE_URL PCC_AUTH0_AUDIENCE PCC_AUTH0_SECRET PCC_BASE_URL LFX_V2_SERVICE; do grep -qE "^${key}=.+" apps/lfx-one/.env || missing+=("$key") done if [ ${#missing[@]} -gt 0 ]; then printf "Missing env vars: %s\n" "${missing[*]}" else echo "All critical env vars are populated." fi
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.
- 1mo ago Changed 70c0e284670a
- 2mo ago First seen · 137 lines · 44 tokens per session scan A 0a851912474f
setup is a skill published in the GitHub repository linuxfoundation/lfx-self-serve (16 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,365 once invoked, about $0.0002 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…