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/self-serve-dev/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/self-serve-dev)<a href="https://agentmods.dev/skills/linuxfoundation/lfx-self-serve/self-serve-dev"><img src="https://agentmods.dev/badge/skills/linuxfoundation/lfx-self-serve/self-serve-dev/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/self-serve-dev"><img src="https://agentmods.dev/badge/skills/linuxfoundation/lfx-self-serve/self-serve-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00065 | $0.03244 |
| Opus 5.5 | $0.00026 | $0.01298 |
| Sonnet 5.5 | $0.00013 | $0.00649 |
| Haiku 4.5 | $0.00006 | $0.00324 |
Grade A, and why
self-serve-dev 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 today.
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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LFX One Development Guide
You are helping a contributor build within the LFX One codebase. This skill handles all development work: creating new features, fixing bugs, modifying existing code, refactoring, and full end-to-end feature builds.
Important: You are integrating features within existing architecture — not making architectural decisions. If the work requires changes to routing, auth, middleware, or infrastructure, flag it for a code owner.
Pre-edit hygiene
Before every meaningful edit:
- Re-read the file with
view— do not trust prior conversation history. Files change; context drifts. - Run
yarn check-typesafter multi-file changes to catch type drift early. - Stop and ask if the request conflicts with conventions in
AGENTS.mdor.claude/rules/.
Default to small, atomic changes. If a request spans more than one module or touches both client and SSR server, surface that and ask whether to split.
Step 1: Start from Latest Main & Track Work
Follow the "Starting New Work" rule in development-rules.md — checkout main, pull latest, and create a feature branch before writing any code.
Tracking Issue (GitHub Issue)
Before writing code, ensure the work is tracked:
- Check for an existing issue — a GitHub Issue on
linuxfoundation/lfx-self-serve(e.g. under an epic on the Kanban board). Work on another product's feature that lands in this repo stays tracked in that product's repo — e.g. Mentorship onlinuxfoundation/lfx-mentorship— reference that issue rather than duplicating it here - Create one if needed — create a GitHub Issue via
gh issue create(use--repo linuxfoundation/<repo>when the feature belongs to a sibling product, so the issue lands in that product's tracker); do not create Jira tickets - Branch name must include the issue number:
feat/issue-<number>,fix/issue-<number>for a GitHub Issue in this repo, orfeat/<repo>-<number>(e.g.feat/lfx-mentorship-123) for one in another repo - Reference
.claude/rules/commit-workflow.mdfor naming conventions
What ships with it
4 files 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.
- today Changed · +8 lines 33c52437cdf3
- 26d ago Changed f20e44e0b01f
- 28d ago Changed a72526564667
- 1mo ago Changed cbabcb00d159
- 1mo ago Changed b432343a23b5
- 2mo ago First seen · 258 lines · 65 tokens per session scan A 345f18965673
self-serve-dev is a skill published in the GitHub repository linuxfoundation/lfx-self-serve (16 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 3,244 once invoked, about $0.0003 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
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
dev-runtime
How the Node side of a dev stack runs without haven, and the backend host: pnpm dev (UI built once, backend reloading), pnpm dev:hmr (adds the Vite ui lane), tools/dev-runtime (api + worker in one Node process), backend reload on a file change, the debounce (quiet window + max wait), ports derived from PORT. Use when…
api-design
Use when settling the contract of an API you expose, before implementation: resources/URLs, REST vs GraphQL, versioning, one RFC 9457 error envelope, pagination, idempotency — emitted as OpenAPI 3.1. NOT implementing the endpoints (that is fastapi/nestjs/go/nodejs), NOT auth hardening (that is secure-coding), NOT…