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/openshift/lightspeed-agentic-operator/review-prnpx skills add openshift/lightspeed-agentic-operator --skill review-prgit clone --depth 1 https://github.com/openshift/lightspeed-agentic-operatorWhat 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.00018 | $0.01331 |
| Opus 5 | $0.00009 | $0.00665 |
| Sonnet 5 | $0.00004 | $0.00266 |
| Haiku 4.5 | $0.00002 | $0.00133 |
Grade A, and why
review-pr 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 3d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review PR
When asked to review a PR, follow this structured approach.
1. Fetch Latest Changes
Always fetch the latest PR state before reviewing. The cached PR data may be stale.
git fetch upstream pull/<PR_NUMBER>/head:pr-<PR_NUMBER>
git log pr-<PR_NUMBER> --oneline -10
git diff upstream/main...pr-<PR_NUMBER> --stat
For follow-up reviews, re-fetch to get new commits:
git fetch upstream pull/<PR_NUMBER>/head:pr-<PR_NUMBER> --force
Read diffs per area (controllers, reconcilers, assets, tests) rather than one massive diff.
2. Understand What It Implements
- Summarize the feature/fix in 2-3 sentences
- Identify the flow: entry point -> processing -> output
- Map which files serve which role (controller, reconciler, assets, CRD, test)
3. Evaluate How It's Implemented
Only raise issues if you have a concrete concern — not as a checklist to fill:
- Architecture: Is logic clearly in the wrong layer? (e.g. business logic leaking into controller/reconciler)
- Error handling: Are errors silently swallowed with
_ = err, or is error wrapping missing where failure is plausible? - Duplication: Is the same logic copy-pasted, not just similar-looking?
- For deep analysis, use the find-duplication skill
- Dead code / docs: Is there obviously unused code or a doc update that's clearly missing?
- For comprehensive analysis, use the find-dead-code skill
- Complexity: Are functions overly complex with high cyclomatic/cognitive complexity?
- For detailed analysis, use the find-complexity skill
Skip this section if nothing stands out.
4. Assess Naming
Only flag naming if it is genuinely misleading or inconsistent with established patterns in the codebase. Do not flag stylistic preferences or minor wording variations.
- Check against Go conventions: exported functions start with uppercase, package-level names don't stutter
- Verify interface names end in
-er(Reader, Writer, Reconciler)
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.
- 3d ago First seen · 118 lines · 18 tokens per session scan A 7684aaba667f
review-pr is a skill published in the GitHub repository openshift/lightspeed-agentic-operator (10 stars, last pushed 4d ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,331 once invoked, about $0.0001 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-31.
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…