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.
npx agentmods add commands/gotempsh/temps/monitorsgit 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/monitors)<a href="https://agentmods.dev/commands/gotempsh/temps/monitors"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/monitors.svg" alt="Measured on agentmods" 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.00820 |
| Opus 5 | $0.00000 | $0.00410 |
| Sonnet 5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
monitors 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
monitors command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
monitors (alias: monitoring)
Manage uptime monitors for status pages
Subcommands:
list(ls) - List all monitors for a projectcreate(add) - Create a new monitor for a projectshow- Show monitor details and current statusremove(rm) - Delete a monitorstatus- Get current status — all monitors for a project, or a single monitor by IDhistory- Get monitor uptime history
monitors list (alias: ls)
List all monitors for a project
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--project-id <id> |
Project ID | - | Yes |
--json |
Output in JSON format | - | No |
monitors create (alias: add)
Create a new monitor for a project
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--project-id <id> |
Project ID | - | Yes |
-n, --name <name> |
Monitor name | - | No |
-t, --type <type> |
Monitor type (http, tcp, ping) | - | No |
-i, --interval <seconds> |
Check interval in seconds (60, 300, 600, 900, 1800) | - | No |
--check-path <path> |
HTTP health-check path (must start with "/", e.g. /api/healthz). Defaults to "/" for HTTP monitors. | - | No |
--environment-id <id> |
Environment ID (default: 0 for production) | - | No |
-y, --yes |
Skip confirmation prompts (for automation) | - | No |
monitors show
Show monitor details and current status
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--id <id> |
Monitor ID | - | Yes |
--json |
Output in JSON format | - | No |
monitors remove (alias: rm)
Delete a monitor
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--id <id> |
Monitor ID | - | Yes |
-f, --force |
Skip confirmation | - | No |
-y, --yes |
Skip confirmation prompts (alias for --force) | - | 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.
- 2d ago First seen · 93 lines · 0 tokens per session scan A 28d5a8cb88f4
monitors is a command published in the GitHub repository gotempsh/temps (712 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 820 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-03.
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.
pr-check
Run all local CI checks before creating a PR.