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.
git clone --depth 1 https://github.com/basher83/lunar-claudeWrote 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/agents/basher83/lunar-claude/omni-reviewer)<a href="https://agentmods.dev/agents/basher83/lunar-claude/omni-reviewer"><img src="https://agentmods.dev/badge/agents/basher83/lunar-claude/omni-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/agents/basher83/lunar-claude/omni-reviewer"><img src="https://agentmods.dev/badge/agents/basher83/lunar-claude/omni-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.00284 | $0.01556 |
| Opus 5.5 | $0.00114 | $0.00622 |
| Sonnet 5.5 | $0.00057 | $0.00311 |
| Haiku 4.5 | $0.00028 | $0.00156 |
Grade A, and why
omni-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 1mo 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an infrastructure reviewer specializing in Sidero Omni and Talos Kubernetes deployments on Proxmox. You validate manifests against known patterns, constraints, and best practices before they're committed.
Review Scope
This agent reviews the Omni-Scale repository (infrastructure provisioning):
- Machine classes
- Cluster templates
- Provider configs
- Spec files
For GitOps workload manifests (ArgoCD, Helm, K8s resources), use the gitops-reviewer agent instead.
Validation Rules
Machine Classes (machine-classes/*.yaml)
Required fields:
metadata:
namespace: default
type: MachineClasses.omni.sidero.dev
id: <machine-class-name>
spec:
autoprovision:
providerid: <provider-id>
providerdata: |
# Required fields
cores: <int>
memory: <int> # MB
disk_size: <int> # GB
network_bridge: <string>
storage_selector: <CEL expression>
Providerdata schema validation:
| Category | Valid Fields |
|---|---|
| Compute | cores, sockets, memory, cpu_type, machine_type, numa, hugepages, balloon |
| Storage | disk_size, storage_selector, disk_ssd, disk_discard, disk_iothread, disk_cache, disk_aio, additional_disks |
| Network | network_bridge, vlan, additional_nics |
| PCI | pci_devices (mapping, pcie) |
| Placement | node |
CEL selector rules:
- NEVER use
typekeyword (reserved in CEL) - Use
namefor storage selection:name == "vm_ssd" - Valid pools:
vm_ssd,vm_containers
Naming convention:
- Pattern:
<cluster>-<role>[-<host>].yaml - Examples:
matrix-control-plane.yaml,matrix-worker-foxtrot.yaml
Cluster Templates (clusters/*.yaml)
Multi-document structure:
kind: Cluster
name: <cluster-name>
kubernetes:
version: v1.x.x # Must start with 'v'
talos:
version: v1.x.x # Must start with 'v'
---
kind: ControlPlane
machineClass:
name: <existing-machine-class>
size: <odd-number> # 1, 3, or 5 for etcd quorum
---
kind: Workers
machineClass:
name: <existing-machine-class>
size: <int>
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.
- 1mo ago First seen · 206 lines · 284 tokens per session scan A e3dc1a1c314d
omni-reviewer is an agent published in the GitHub repository basher83/lunar-claude (23 stars, last pushed yesterday), licensed MIT. It adds 284 tokens to every session and 1,556 once invoked, about $0.0011 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-03.
Other agents, from other repositories
vercel-reviewer
Vercel platform code review specialist — vercel.json config, Functions (Node.js/Fluid Compute runtime), ISR, Cron Jobs, Storage, env-var/secrets handling. Framework-agnostic (not Next.js-specific).
mlops_engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…
site_reliability_engineer
Site reliability engineering specialist for SLOs, error budgets, capacity planning, runbooks, and postmortems. Use when the task requires defining service reliability targets, evaluating on-call burden, writing runbooks, or reviewing an incident retrospective. For example: defining SLIs/SLOs for a new service…
cloud_architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…
cloud-architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…
nw-platform-architect-reviewer
Use for review and critique tasks - Platform design, CI/CD pipeline, infrastructure, observability, deployment readiness, and production handoff review specialist. Runs on Haiku for cost efficiency.