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/cloud)<a href="https://agentmods.dev/commands/gotempsh/temps/cloud"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/cloud/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/cloud"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/cloud.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.02594 |
| Opus 5.5 | $0.00000 | $0.01038 |
| Sonnet 5.5 | $0.00000 | $0.00519 |
| Haiku 4.5 | $0.00000 | $0.00259 |
Grade A, and why
cloud 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 11d 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 — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cloud command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
Contents
cloud logincloud logoutcloud whoamicloud statuscloud connectcloud disconnectcloud backup-schedulecloud vpscloud billingcloud console-accesscloud telemetry
cloud
Temps Cloud
Subcommands:
login- Login to Temps Cloudlogout- Logout from Temps Cloudwhoami- Show current Temps Cloud accountstatus- Show this self-hosted instance's Temps Cloud linkconnect- Connect this self-hosted instance using an enrollment codedisconnect- Disconnect this self-hosted instance from Temps Cloudbackup-schedule- The backup schedule that writes to the Temps Cloud destinationvps- Manage cloud VPS instancesbilling- Manage Temps Cloud billing and subscriptionconsole-access- Console access through Temps Cloud (ADR-045) -- Cloud members with the owner/admin role can open this console with no inbound porttelemetry- Where a project’s spans are written — this instance, or Temps Cloud (ADR-041)
cloud login
Login to Temps Cloud
cloud logout
Logout from Temps Cloud
cloud whoami
Show current Temps Cloud account
cloud status
Show this self-hosted instance's Temps Cloud link
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--json |
Output JSON | - | No |
cloud connect
Connect this self-hosted instance using an enrollment code
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--code <code> |
Single-use enrollment code from Temps Cloud | - | Yes |
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.
- 11d ago Changed · +42 lines 28ee85d1307a
- 29d ago Changed · +32 lines 3067045fbf35
- 1mo ago Changed · +129 lines 1e68a5d4d038
- 1mo ago First seen · 169 lines · 0 tokens per session scan A b59606938c89
cloud 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 2,594 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.
Other commands, from other repositories
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
workflow-automation
Integrate AI swarms with GitHub Actions to create intelligent, self-organizing CI/CD pipelines that adapt to your codebase.
workflow-automation
Integrate AI swarms with GitHub Actions to create intelligent, self-organizing CI/CD pipelines that adapt to your codebase.
pipeline-generate
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with pipeline generate in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
rollback-plan
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with rollback plan in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
secrets-audit
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with secrets audit in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.