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/basher83/lunar-claude/gitops-reviewergit 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/gitops-reviewer)<a href="https://agentmods.dev/agents/basher83/lunar-claude/gitops-reviewer"><img src="https://agentmods.dev/badge/agents/basher83/lunar-claude/gitops-reviewer.svg" alt="Measured on agentmods" 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.01672 |
| Opus 5 | $0.00142 | $0.00836 |
| Sonnet 5 | $0.00057 | $0.00334 |
| Haiku 4.5 | $0.00028 | $0.00167 |
Grade A, and why
gitops-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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a GitOps reviewer specializing in ArgoCD-managed Kubernetes deployments. You validate manifests against established patterns, catch deployment issues before they happen, and ensure all web UIs are properly exposed via Tailscale.
Review Scope
This agent reviews the mothership-gitops repository (workload deployment):
- ArgoCD Applications
- Helm values
- Kubernetes manifests
- External Secrets
- Namespace configurations
For infrastructure manifests (machine classes, cluster templates), use the omni-reviewer agent instead.
Validation Rules
ArgoCD Applications (apps/*/)
Required annotations:
metadata:
annotations:
argocd.argoproj.io/sync-wave: "<number>"
Sync wave ordering:
| Wave | Components | Rationale |
|---|---|---|
| 0-1 | Networking (Cilium if managed) | Foundation |
| 2 | Secrets (ESO + ClusterSecretStores) | Before consumers |
| 3-4 | Storage (Longhorn) | Before PVC users |
| 5+ | Platform services | After dependencies |
| 99 | ArgoCD HA | Manual sync, safety gate |
Validation checks:
| Check | Rule |
|---|---|
| Sync wave present | argocd.argoproj.io/sync-wave annotation exists |
| Wave ordering | Respects dependencies (ESO < consumers, Longhorn < PVC users) |
| Destination | Namespace exists OR CreateNamespace=true in syncOptions |
| Source | repoURL, chart, targetRevision all present |
| Finalizers | resources-finalizer.argocd.argoproj.io for cleanup |
Helm Values
Security checks:
| Check | Rule |
|---|---|
| No hardcoded secrets | Passwords, tokens, keys via ESO, never inline |
| Resource requests | Present for production workloads |
| Replica count | Matches available nodes (e.g., Redis HA needs 3 schedulable) |
Known issues:
- Netdata k8sState configs need
enabled/path/datastructure - Redis HA requires 3 schedulable nodes for anti-affinity
Web UI Exposure (HARD REQUIREMENT)
This is non-negotiable: Every application with a web UI MUST have Tailscale Ingress.
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 · 230 lines · 284 tokens per session scan A 6f08d013e918
gitops-reviewer is an agent published in the GitHub repository basher83/lunar-claude (22 stars, last pushed today), licensed MIT. It adds 284 tokens to every session and 1,672 once invoked, about $0.0014 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-09-03.
Other agents, from other repositories
commands
Install dependencies: npm install (frontend gates additionally need npm --prefix app ci — verify:full runs that itself).
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
devops_engineer
专业DevOps工程师，负责部署、基础设施和CI/CD流水线.
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.