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/go-code-reviewnpx skills add openshift/lightspeed-agentic-operator --skill go-code-reviewgit 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.00041 | $0.00856 |
| Opus 5 | $0.00020 | $0.00428 |
| Sonnet 5 | $0.00008 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
go-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 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Code Review
Quick Reference
| Issue Type | Reference |
|---|---|
| Missing error checks, wrapped errors | references/error-handling.md |
| Race conditions, channel misuse | references/concurrency.md |
| Interface pollution, naming | references/interfaces.md |
| Resource leaks, defer misuse | references/common-mistakes.md |
Review Checklist
- All errors are checked (no
_ = err) - Errors wrapped with context (
fmt.Errorf("...: %w", err)) - Resources closed with
deferimmediately after creation - No goroutine leaks (channels closed, contexts canceled)
- Interfaces defined by consumers, not producers
- Interface names end in
-er(Reader, Writer, Handler) - Exported names have doc comments
- No naked returns in functions > 5 lines
- Context passed as first parameter
- Mutexes protect shared state, not methods
Kubernetes Operator Specific
- Owner references set with
controllerutil.SetControllerReference() - Finalizers added/removed safely (check for DeletionTimestamp)
- Context propagated through reconcile loops
- Client errors handled (distinguish NotFound vs other errors)
- Status updates separate from spec changes
- Resource watching pattern: Owned resources tracked via ResourceVersion; external dependencies use explicit watches or indexing as appropriate for the controller
- Reconcile functions are idempotent (safe to call multiple times)
- Resource updates check semantic equality first (
apiequality.Semantic.DeepEqual) - Return
ctrl.Result{Requeue: true}for transient issues, errors for permanent failures - RBAC markers (
//+kubebuilder:rbac) present for all resource access in controllers
When to Load References
- Reviewing error return patterns → error-handling.md
- Reviewing goroutines/channels → concurrency.md
- Reviewing type definitions → interfaces.md
- General Go review → common-mistakes.md
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 85 lines · 41 tokens per session scan A b9dce362394c
go-code-review is a skill published in the GitHub repository openshift/lightspeed-agentic-operator (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 41 tokens to every session and 856 once invoked, about $0.0002 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
layered-architecture-types
Enforce primitive-at-edges / strong-types-in-Business layering and the toBus/fromBusResponse/toDB converter pattern. Use when writing, editing, or auditing Go files under app/, business/domain/, or .../stores/db.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-observability
Golang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for…
golang-data-structures
Golang data structures — slices (internals, capacity growth, preallocation, slices package), maps (internals, hash buckets, maps package), arrays, container/list/heap/ring, strings.Builder vs bytes.Buffer, generic collections, pointers (unsafe.Pointer, weak.Pointer), and copy semantics. Use when choosing or optimizing…
golang-dependency-management
Dependency management for Golang projects — go.mod and go.sum, go get install and upgrade flows, Minimal Version Selection, conflict resolution with replace/exclude/retract, govulncheck scanning of the module tree, outdated dependency and binary size auditing, vendoring, tool directives, and go.work workspaces. Use…
golang-spf13-viper
Golang configuration library using spf13/viper — layered precedence (flag > env > file > KV > default), BindPFlag/BindPFlags, SetEnvPrefix + SetEnvKeyReplacer + AutomaticEnv, ReadInConfig + ConfigFileNotFoundError, Unmarshal + mapstructure struct tags, Sub for sub-trees, WatchConfig + OnConfigChange for hot reload…