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/self-serve-code-reviewnpx skills add linuxfoundation/lfx-self-serve --skill self-serve-code-reviewgit 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-code-review)<a href="https://agentmods.dev/skills/linuxfoundation/lfx-self-serve/self-serve-code-review"><img src="https://agentmods.dev/badge/skills/linuxfoundation/lfx-self-serve/self-serve-code-review.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.00102 | $0.02044 |
| Opus 5 | $0.00051 | $0.01022 |
| Sonnet 5 | $0.00020 | $0.00409 |
| Haiku 4.5 | $0.00010 | $0.00204 |
Grade A, and why
self-serve-code-review 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self Serve Code Review
Reviewer scope and the signal bar are owned by the copilot-code-reviewer
skill (.github/skills/copilot-code-reviewer/SKILL.md); this skill assumes
those and covers only the line-level judgment. Read enough surrounding code
to judge each hunk in its real context — for a server change, the middleware →
controller → service path it sits on; for an Angular change, the component, its
template, and the signals and services it consumes.
A diff alone is not enough. For each non-trivial hunk, read the whole changed
function, not just the diff lines, and Grep for callers and sibling
implementations of the same pattern to confirm the change matches how the repo
already does it — convention drift is a finding even when the code "works". For
a proxy change, read one layer past the diff: the upstream contract the call
must mirror, not just the local shape.
The house standards
The repo defines its own standards; hold the diff to them, and name the documented source in any standards finding. Read the parts relevant to the diff before judging, every run, because the standards belong to the repo and move with it. They live in:
CLAUDE.md— the source-of-truth order, the domain language (PCC, ED, Admin Mode, personas, L2), commit/PR conventions, and the global "what NOT to do" list..claude/rules/—component-organization.md(Angular signal structure,model()vsWritableSignal, the DELETE→CREATE rule for full component replacements),logging-patterns.md(the PinoLoggerService, operation lifecycle, controller-vs-service logging responsibility),styling.md(Tailwind,lfxColors,flex + flex-col + gap-*notspace-y-*),ssr-safety.md, anddevelopment-rules.md(the shared package, M2M-vs-user tokens, upstream-contract verification, code-quality rules).- The four
docs/reviews/checklists —frontend-checklist.md(PrimeNG wrapper strategy: prefer the LFX wrapper over a raw<p-*>in feature templates unless a documented exception applies, no function calls in render-time expressions — interpolation and property bindings should read signals or pipes, not call methods that re-run every change detection; event bindings like(click)="save()"are the normal exception — component organization),backend-checklist.md(the three-file service/controller/route pattern, controller-vs-service separation, custom error classes, user bearer tokens vs M2M, upstream API validation, protected files),shared-and-sql-checklist.md, anddocs-checklist.md.
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 · 152 lines · 102 tokens per session scan A 0ebcf176d52c
self-serve-code-review is a skill published in the GitHub repository linuxfoundation/lfx-self-serve (11 stars, last pushed today), licensed MIT. It adds 102 tokens to every session and 2,044 once invoked, about $0.0005 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…