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/gotempsh/tempsWrote 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/gotempsh/temps/server)<a href="https://agentmods.dev/commands/gotempsh/temps/server"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/server/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/commands/gotempsh/temps/server"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/server.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.00000 | $0.00518 |
| Opus 5.5 | $0.00000 | $0.00207 |
| Sonnet 5.5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
server 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 29d 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
server command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
server
Resource usage of the machine running the Temps control plane (what /monitoring/server shows)
Subcommands:
status- Latest CPU, memory, disk, block I/O and network I/O sample for the control-plane hostmetrics- Time series of one control-plane host metric, e.g. node.cpu_percent or node.network_rx_bytes_totaldocker-disk-usage(df) - Docker disk usage by images, containers, volumes and build cache (docker system df) on the control-plane host
server status
Latest CPU, memory, disk, block I/O and network I/O sample for the control-plane host
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--node <id> |
Node ID (0 = control plane) | 0 |
No |
--json |
Output in JSON format | - | No |
server metrics
Time series of one control-plane host metric, e.g. node.cpu_percent or node.network_rx_bytes_total
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--metric <name> |
Metric name (node.cpu_percent, node.memory_used_bytes, node.disk_used_bytes, node.disk_read_bytes_total, node.network_tx_bytes_total, ...) | - | Yes |
--range <range> |
Time window: 1h, 6h, 24h, 7d | 1h |
No |
--node <id> |
Node ID (0 = control plane) | 0 |
No |
--json |
Output in JSON format | - | No |
server docker-disk-usage (alias: df)
Docker disk usage by images, containers, volumes and build cache (docker system df) on the control-plane host
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--node <id> |
Node ID (0 = control plane) | 0 |
No |
--json |
Output in JSON format | - | No |
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.
- 29d ago First seen · 51 lines · 0 tokens per session scan A 4e1570fe51f1
server is a command published in the GitHub repository gotempsh/temps (848 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 518 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-09-19.
Other commands, from other repositories
terraform-scaffold
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with terraform scaffold in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
cost-optimize
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with cost optimize in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
cost-optimize
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with cost optimize in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
monitor-setup
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with monitor setup in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
monitor-setup
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with monitor setup in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
devops
Designs CI/CD pipelines, infrastructure, observability, and deployment strategy. Use when preparing platform readiness for a feature.