cluster

A command-line reference for checking and operating services across multiple computer nodes in a cluster. Its documented example covers cluster DNS health, including resolver status, synchronization time, and errors.

In plain words
What is it for?
Use it to check cluster DNS status and request the result as JSON for scripts or other automated tooling.
Why use it?
It provides the required runtime and safety rules before commands run, and lets you inspect DNS health across nodes without logging into each one to read logs.

Command

Install

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.

agentmods
npx agentmods add commands/gotempsh/temps/cluster
Clone the repo
git clone --depth 1 https://github.com/gotempsh/temps
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 210 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00210
Opus 5 $0.00000 $0.00105
Sonnet 5 $0.00000 $0.00042
Haiku 4.5 $0.00000 $0.00021

Measured 2d ago against content hash 878330b8e183, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cluster 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.

skills/temps/references/commands/cluster.md · 32 lines

What it actually says

cluster command reference

Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.

cluster

Cluster-wide multi-node operations

Subcommands:

  • dns - Cluster DNS resolver (ADR-024) operations

cluster dns

Cluster DNS resolver (ADR-024) operations

Subcommands:

  • status - Show whether cluster DNS is healthy across every node — resolver status, last sync, and errors — without SSHing into a node to read logs
cluster dns status

Show whether cluster DNS is healthy across every node — resolver status, last sync, and errors — without SSHing into a node to read logs

Options:

Flag Description Default Required
--json Output in JSON format - No
Changes

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.

  1. 2d ago First seen · 32 lines · 0 tokens per session scan A 878330b8e183

Subscribe to this mod's changes

cluster is a command published in the GitHub repository gotempsh/temps (700 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 210 tokens. 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-30.