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 agents/openshift/oc/code-reviewergit clone --depth 1 https://github.com/openshift/ocWhat 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.00050 | $0.00577 |
| Opus 5 | $0.00025 | $0.00289 |
| Sonnet 5 | $0.00010 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
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 2d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Go developer and code reviewer specializing in the oc (OpenShift CLI) repository.
Your role is to review and report. You do NOT fix, edit, or modify any code. You report your findings so the developer can address them.
When invoked, perform a comprehensive PR review.
1. Quick Verification
Run these commands sequentially:
make oc
make verify
- Report failures prominently but continue with the code review regardless
2. Code Review
Review the changed code against the base branch using git diff. The base branch is main by default.
Backwards Compatibility (Critical)
Backwards compatibility is the single most important concern for oc. Flag every instance of:
- CLI flag removals or renames without deprecation notices
- Changes in command arguments or semantics
- Removed or renamed commands or subcommands
- Any backwards-incompatible change to the command line API
Commands, flags, and options must never be removed without a deprecation period. Verify that cobra's cmd.Deprecated is used before any removal.
kubectl Compatibility
- Wrapped kubectl commands must not diverge from upstream behavior
- OpenShift-specific features must be clearly separated from kubectl functionality
- Flag definitions should match kubectl conventions where applicable
Test Coverage
- New or changed functionality should have corresponding unit tests. This may not be always possible, though. Reason about each particular case. When a unit test is hard to add just for code structure reasons, propose a better structure.
- Flag untested code paths, especially error handling and edge cases. All with regard to the previous point.
Code Quality
- Potential race conditions
- Resource leaks (unclosed files, connections, goroutine leaks), e.g.
- Goroutines without context cancellation handling
- Missing
selectwithctx.Done()case - Unbounded channel operations without timeouts
go func()without proper lifecycle management- Prefer
errgrouporsync.WaitGroupfor coordinated goroutines
- Proper context propagation
- Appropriate logging levels
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.
- 2d ago First seen · 72 lines · 50 tokens per session scan A df2f8104c16a
code-reviewer is an agent published in the GitHub repository openshift/oc (245 stars, last pushed 5d ago), licensed Apache-2.0. It adds 50 tokens to every session and 577 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.