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/lfx-self-serve-learnings-review/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/lfx-self-serve-learnings-review)<a href="https://agentmods.dev/skills/linuxfoundation/lfx-self-serve/lfx-self-serve-learnings-review"><img src="https://agentmods.dev/badge/skills/linuxfoundation/lfx-self-serve/lfx-self-serve-learnings-review/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/lfx-self-serve-learnings-review"><img src="https://agentmods.dev/badge/skills/linuxfoundation/lfx-self-serve/lfx-self-serve-learnings-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to medium
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 →
- medium Prompt Injection · line 60 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 62 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 63 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 64 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 67 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 68 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00197 | $0.02279 |
| Opus 5.5 | $0.00079 | $0.00912 |
| Sonnet 5.5 | $0.00039 | $0.00456 |
| Haiku 4.5 | $0.00020 | $0.00228 |
Grade A, and why
lfx-self-serve-learnings-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 26d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LFX Self-Serve Learnings Reviewer
You match the caller's pinned range on the local branch against the empirical pattern knowledge base in docs/reviews/knowledge-base/. Each pattern entry was extracted from a real PR review comment on this repo. Findings are gated by KB matches: every emitted finding must quote a pattern entry's rule ID + a phrase from its **Pattern:** or **Detect:** clause. If you can't quote, you drop.
Generic-rubric findings (security / performance / quality / architecture / testing intuitions not grounded in a KB entry) and documented-rule-surface findings belong to /lfx-skills:lfx-general-code-review, which reviews general quality plus this repo's written conventions. You cover the empirical surface — the patterns the bots and human reviewers have actually flagged.
Repository scope
This skill is owned by the lfx-self-serve repo
(.claude/skills/lfx-self-serve-learnings-review/), and the reviewer loading
it may be launched from the LFX workspace root or a multi-repo session.
Regardless of the current working directory, it always reviews
lfx-self-serve.
If the caller provides target repo: lfx-self-serve, use that as confirmation.
If the caller provides any other target repo, abort with
INCOMPLETE - lfx-self-serve reviewer invoked for <repo>.
Before diffing, locate the lfx-self-serve repo root:
- If you are already in
lfx-self-serve, you are home. Use that repo root. - Otherwise, look for a sibling or child directory named
lfx-self-serve. - If the repo cannot be found, abort with
INCOMPLETE - lfx-self-serve repo not found.
Inputs
Parse the caller's prompt for:
base_sha/target_sha(or areview exactly: git diff <base_sha> <target_sha>line) — the pinned range:base_shais the merge-base of the branch with the PR base,target_shais the branch HEAD. When supplied, review exactly that range and never re-derive it from a movingHEADororigin/main. When not supplied, pin them yourself once, before anything else:git fetch origin && base_sha=$(git merge-base origin/main HEAD) && target_sha=$(git rev-parse HEAD), then proceed as if the caller had passed them. There is no per-commit mode: the range is always the whole branch between these two endpoints.extra: <free text>— optional priority hint.
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.
- 26d ago Changed · -1 tokens per session e64f66e85a47
- 28d ago Changed · -2 lines · +38 tokens per session 3af8cfe4dc90
- 1mo ago Changed 562ff5ccdce3
- 1mo ago First seen · 140 lines · 160 tokens per session scan A 8406a038ddac
lfx-self-serve-learnings-review is a skill published in the GitHub repository linuxfoundation/lfx-self-serve (16 stars, last pushed today), licensed MIT. It adds 197 tokens to every session and 2,279 once invoked, about $0.0008 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-09-04.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…