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/setupnpx skills add linuxfoundation/lfx-self-serve --skill setupgit 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.00044 | $0.01347 |
| Opus 5 | $0.00022 | $0.00674 |
| Sonnet 5 | $0.00009 | $0.00269 |
| Haiku 4.5 | $0.00004 | $0.00135 |
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 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 — 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 v22+ — 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.
- 2d 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 (11 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 1,347 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-30.
Other skills, from other repositories
nemoclaw-contributor-implement-issue
Implement an accepted NemoClaw GitHub issue in the current checkout. Use when a user asks to pick up an issue for implementation, implement or fix a named issue, or add the issue's tests. Confirm accepted scope, deliver the smallest independently valuable capability slice, and record validation and remaining gates…
amazon-bestseller-listing
Amazon Best Sellers listing scraper: extract product cards from any Amazon Best Sellers (zgbs) or /gp/bestsellers/ category page — returns rank (position on chart), asin, title, url, image, imageAlt, price, stars, reviewCount, ratingRaw per item, plus category metadata (categoryName, categoryFullName, categoryUrl) and…
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
cabloy-worktree-environment
This skill must be used only when the user explicitly invokes /cabloy-worktree-environment or explicitly asks to perform the named Cabloy worktree-environment setup. It prepares a confirmation-gated, worktree-local Vona and Zova runtime environment for a linked Cabloy Basic or Cabloy Start Git worktree using Git…
shopify-hydrogen
Hydrogen storefront implementation cookbooks. Some of the available recipes are: B2B Commerce, Bundles, Combined Listings, Custom Cart Method, Dynamic Content with Metaobjects, Express Server, Google Tag Manager Integration, Infinite Scroll, Legacy Customer Account Flow, Markets, Partytown + Google Tag Manager…