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 commands/basher83/lunar-claude/bootstrap-gitopsgit 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/commands/basher83/lunar-claude/bootstrap-gitops)<a href="https://agentmods.dev/commands/basher83/lunar-claude/bootstrap-gitops"><img src="https://agentmods.dev/badge/commands/basher83/lunar-claude/bootstrap-gitops.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.00019 | $0.01618 |
| Opus 5 | $0.00010 | $0.00809 |
| Sonnet 5 | $0.00004 | $0.00324 |
| Haiku 4.5 | $0.00002 | $0.00162 |
Grade A, and why
bootstrap-gitops 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitOps Bootstrap
Deploy the GitOps stack onto an existing talos-prod-01 cluster.
NOTE: This command encodes the full bootstrap sequence to avoid chicken-and-egg issues discovered during DR drills. Do not simplify or reorder phases.
Pre-flight Gate
STOP if omni-talos skill is not loaded.
Check: Do you have knowledge of provider-ctl.py and the provider operations table?
If not, instruct user:
Required setup not complete. Run this chain first:
/omni-scale:omni-prime && /omni-scale:status && /omni-scale:omni-talos
Then re-run /omni-scale:bootstrap-gitops
Instructions
Phase 1: Create Bootstrap Secret
Outcome: external-secrets namespace exists with universal-auth-credentials
secret containing Infisical credentials.
Create namespace external-secrets and secret using kubectl. Secret requires:
$INFISICAL_UNIVERSAL_AUTH_CLIENT_ID$INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET
If env vars not set, stop and inform user with exact var names needed.
Phase 2: Install Cilium (CNI)
Outcome: Cilium installed, all nodes become Ready.
Why first: GitOps-managed CNI creates scheduling deadlock. Nodes stay NotReady without CNI, pods can't schedule, ArgoCD can't deploy CNI. Break cycle with manual Cilium install.
Talos requirements:
kubeProxyReplacement=true— Talos disables kube-proxyk8sServiceHost— Must be control plane IP (not ClusterIP)cgroupsettings — Talos uses cgroupv2 with specific mount paths
Get control plane IP first:
kubectl get nodes -l node-role.kubernetes.io/control-plane -o jsonpath='{.items[0].status.addresses[?(@.type=="InternalIP")].address}'
Install with Talos-compatible settings:
helm repo add cilium https://helm.cilium.io/
helm repo update cilium
helm install cilium cilium/cilium \
--namespace kube-system \
--set ipam.mode=kubernetes \
--set kubeProxyReplacement=true \
--set k8sServiceHost=<CONTROL_PLANE_IP> \
--set k8sServicePort=6443 \
--set cgroup.autoMount.enabled=false \
--set cgroup.hostRoot=/sys/fs/cgroup
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 · 218 lines · 19 tokens per session scan A 30b459d361bc
bootstrap-gitops is a command published in the GitHub repository basher83/lunar-claude (22 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 1,618 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-09-03.
Other commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
account
This API allows you to manage your Scaleway Projects.
deploy
Build, test, deploy with staged rollout.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
integrate
/forge:integrate is the integration assistant for connecting your project to external services. It covers version control (GitHub, GitLab), monitoring (Sentry, Datadog), communication (Slack, Discord), databases (PostgreSQL, Redis, MongoDB), and cloud platforms (AWS, GCP, Vercel, Netlify). For each service, it checks…
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.