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/alarms)<a href="https://agentmods.dev/commands/gotempsh/temps/alarms"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/alarms/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/alarms"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/alarms.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.01144 |
| Opus 5.5 | $0.00000 | $0.00458 |
| Sonnet 5.5 | $0.00000 | $0.00229 |
| Haiku 4.5 | $0.00000 | $0.00114 |
Grade A, and why
alarms 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 22d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
alarms command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
alarms (alias: alarm)
List, acknowledge, and resolve alarms (container crashes, uptime, metrics, databases)
Subcommands:
list(ls) - List alarms, newest firstsummary- Show active alarm counts by status, severity, and typeack(acknowledge) - Acknowledge alarms by ID, or every alarm matching the filters with --allresolve- Resolve alarms by ID, or every alarm matching the filters with --all
alarms list (alias: ls)
List alarms, newest first
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-p, --project <slug> |
Project slug (auto-detected from .temps/config.json or TEMPS_PROJECT) | - | No |
--project-id <id> |
Project ID (instead of --project) | - | No |
--system |
Target host-wide system alarms (disk space, worker nodes) instead of a project | - | No |
--status <status> |
Filter by status (firing, acknowledged, resolved) | - | No |
--severity <severity> |
Filter by severity (info, warning, critical) | - | No |
--type <type> |
Filter by alarm type (e.g. container_crash) | - | No |
--environment-id <id> |
Filter by environment ID | - | No |
--deployment-id <id> |
Filter by deployment ID | - | No |
--page <n> |
Page number (default: 1) | - | No |
--page-size <n> |
Items per page (default: 20, max: 100) | - | No |
--json |
Output in JSON format | - | No |
alarms summary
Show active alarm counts by status, severity, and type
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-p, --project <slug> |
Project slug (auto-detected from .temps/config.json or TEMPS_PROJECT) | - | No |
--project-id <id> |
Project ID (instead of --project) | - | No |
--system |
Target host-wide system alarms (disk space, worker nodes) instead of a project | - | 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.
- 22d ago First seen · 88 lines · 0 tokens per session scan A ccf410883601
alarms 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 1,144 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-26.
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.