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/deployments)<a href="https://agentmods.dev/commands/gotempsh/temps/deployments"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/deployments/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/deployments"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/deployments.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.01525 |
| Opus 5.5 | $0.00000 | $0.00610 |
| Sonnet 5.5 | $0.00000 | $0.00305 |
| Haiku 4.5 | $0.00000 | $0.00153 |
Grade A, and why
deployments 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 6d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
deployments command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
deployments (alias: deploys)
Manage deployments
Subcommands:
list(ls) - List deploymentsstatus- Show deployment statusrollback- Rollback to previous deploymentcancel- Cancel a running deploymentpause- Pause a deploymentresume- Resume a paused deploymentteardown- Teardown a deployment and remove all resourceslogs- Show deployment build logscontainer-logs- Show live container logs, including retained failed deploymentsfailure-report- Preview or send a redacted deploy-failure trace
deployments list (alias: ls)
List deployments
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-p, --project <project> |
Project slug or ID | - | No |
-e, --environment <env> |
Filter by environment name (client-side) | - | No |
--environment-id <id> |
Filter by environment ID (server-side) | - | No |
-n, --limit <number> |
Limit results | 10 |
No |
--page <n> |
Page number | - | No |
--per-page <n> |
Items per page | - | No |
--json |
Output in JSON format | - | No |
deployments status
Show deployment status
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-p, --project <project> |
Project slug or ID (defaults to the linked project) | - | No |
-d, --deployment-id <id> |
Deployment ID | - | Yes |
--json |
Output in JSON format | - | No |
deployments rollback
Rollback to previous deployment
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-p, --project <project> |
Project slug or ID (defaults to the linked project) | - | No |
-e, --environment <env> |
Target environment | production |
No |
--to <deployment> |
Rollback to specific deployment ID | - | 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.
- 6d ago Changed 6dea215b0310
- 1mo ago Changed · +17 lines 4256562e524b
- 1mo ago First seen · 156 lines · 0 tokens per session scan A 7063437339bc
deployments is a command published in the GitHub repository gotempsh/temps (846 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,525 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.