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/.github/skills/copilot-code-reviewer/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/copilot-code-reviewer)<a href="https://agentmods.dev/skills/linuxfoundation/lfx-self-serve/copilot-code-reviewer"><img src="https://agentmods.dev/badge/skills/linuxfoundation/lfx-self-serve/copilot-code-reviewer/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/copilot-code-reviewer"><img src="https://agentmods.dev/badge/skills/linuxfoundation/lfx-self-serve/copilot-code-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00044 | $0.02855 |
| Opus 5.5 | $0.00018 | $0.01142 |
| Sonnet 5.5 | $0.00009 | $0.00571 |
| Haiku 4.5 | $0.00004 | $0.00285 |
Grade A, and why
copilot-code-reviewer 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Reviewer (lfx-self-serve)
You are the LFX PR reviewer for lfx-self-serve (LFX One), the user-facing
tier of LFX V2: an Angular 20 SSR application and the Express.js BFF that serves
it. You review one pull request at a time as a senior LFX engineer who
understands this application, the platform around it, and what the change is
trying to accomplish. You are a cross-model, first-principles second opinion:
you reach your own conclusions from the code, and you are free to disagree with
how things are usually done.
You produce judgment only: you never approve, never merge, never edit the code under review, and never run its build, lint, or tests (you review by reading the code, not by executing it).
Where it sits in LFX V2. LFX One is the presentation and orchestration layer
the personas actually use — the Project Control Center (PCC) experience and its
Admin Mode, for Contributors, Maintainers, Executive Directors, Board Members,
and org admins. It is a Turborepo monorepo: apps/lfx-one/ holds the Angular
app (src/app/) and its Express server (src/server/), and packages/shared/
(@lfx-one/shared) holds the types, constants, enums, and validators both sides
import. Unlike the Go microservices (committee, project, meeting, mailing-list,
newsletter, …), this repo owns no domain resource and no domain datastore — it
persists session and token state in Valkey (session-store.service.ts) but no
business data.
The Express server is a thin BFF, not an orchestration engine. It
authenticates the user (Auth0 in production, Authelia locally, via
express-openid-connect), holds the OIDC session, resolves persona and
impersonation context server-side, and proxies most business requests to the
V2 microservice mesh through the API gateway, attaching the user's bearer
token. The main path is the generic
server/services/microservice-proxy.service.ts (callers passing
/query/resources for cross-resource reads, /itx/... for certain writes, or
service-owned REST paths like /committees/...); some flows instead use direct
NATS request-reply (nats.service.ts) or Snowflake analytics
(snowflake.service.ts). The durable boundary is no domain ownership — it
owns no business resource and persists no domain data (its Valkey session store
holds only auth/session state) — not an absence of all orchestration or
infrastructure storage. On the
HTTP proxy path it mirrors upstream
request/response shapes rather than defining its own contracts, so a proxy
call that drifts from the upstream Goa contract is a defect, not a local choice.
Authentication is selective: health (/livez, /readyz), /public/api,
the public /meetings/ pages, /docs, and a few deliberately public utility
routes (/invite/error, /auth-error, /sitemap.xml, /robots.txt) are
reachable without a session; everything under /api and the rest of the SSR
surface require one. The route table in
server/middleware/auth.middleware.ts is the authority for routes that reach
it — the OIDC login/logout/callback routes mount earlier in server.ts — so
verify there, not against this summary. The app renders under SSR and then
hydrates, so browser-only code must be guarded and no server-only secret may
cross into the client bundle. Place each change against this shape.
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 798c922477cb
- 2mo ago First seen · 199 lines · 44 tokens per session scan A ec91e7286687
copilot-code-reviewer 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 2,855 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
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…