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/statusgit 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/status)<a href="https://agentmods.dev/commands/basher83/lunar-claude/status"><img src="https://agentmods.dev/badge/commands/basher83/lunar-claude/status.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.00008 | $0.00420 |
| Opus 5 | $0.00004 | $0.00210 |
| Sonnet 5 | $0.00002 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
status 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.
What it actually says
Cluster Status
Quick health check for Omni-managed Talos cluster and GitOps stack.
Required Data
Omni Cluster
- Cluster phase (Running/Provisioning/etc)
- Node count (control plane vs workers)
- Overall health status
Kubernetes Nodes
- Ready status for each node
- Role (control-plane vs worker)
- Kubernetes version
- Talos version
- Node IPs
ArgoCD Applications
- Sync status (per app)
- Health status (per app)
- List any apps NOT Synced+Healthy
External Secrets
- ClusterSecretStore count and health
- ExternalSecret count, sync status
- List any secrets failing to sync
Storage (Longhorn)
- Volume state (attached vs detached)
- Volume robustness (healthy vs degraded)
- List any volumes not attached+healthy
Output Format
## Omni-Scale Status Report
### Omni Cluster: talos-prod-01
- Phase: [status]
- Nodes: [X] control plane, [Y] workers
- Health: [status]
### Kubernetes
- Nodes Ready: [X/Y]
- Version: [version]
- Talos: [version]
[Node table with roles and IPs]
### ArgoCD Applications
- Total: [N]
- Synced: [N], OutOfSync: [N]
- Healthy: [N], Degraded: [N]
[Table showing any non-healthy/non-synced apps]
### External Secrets
- ClusterSecretStores: [N] healthy
- ExternalSecrets: [N] synced, [N] failed
[List any failing secrets]
### Storage (Longhorn)
- Volumes: [N]
- Healthy: [N]
- Degraded: [N]
[List any unhealthy volumes]
### Issues Found
[List problems or "None"]
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 · 84 lines · 8 tokens per session scan A 52b773653bc7
status is a command published in the GitHub repository basher83/lunar-claude (22 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 420 once invoked, about $0.0000 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.