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/status-pages)<a href="https://agentmods.dev/commands/gotempsh/temps/status-pages"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/status-pages/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/status-pages"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/status-pages.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.01555 |
| Opus 5.5 | $0.00000 | $0.00622 |
| Sonnet 5.5 | $0.00000 | $0.00311 |
| Haiku 4.5 | $0.00000 | $0.00155 |
Grade A, and why
status-pages 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 4d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
status-pages command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
status-pages (alias: status-page)
Publish public status pages for selected monitors
Subcommands:
list(ls) - List a project's status pagescreate- Create a draft status pageshow- Show a status pageupdate- Change the title, description or monitor selectionpublish- Publish the page at its public URLunpublish- Unpublish; the public URL returns 404 immediatelyrotate-url- Replace the public URL; the old one stops workingdelete(rm) - Delete a status page; its public URL returns 404 immediatelydomains(domain) - Serve a status page on your own hostname
status-pages list (alias: ls)
List a project's status pages
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--project-id <id> |
Project ID | - | Yes |
--json |
Output in JSON format | - | No |
status-pages create
Create a draft status page
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--project-id <id> |
Project ID | - | Yes |
-t, --title <title> |
Public page title | - | Yes |
-d, --description <text> |
Public description | - | No |
-m, --monitor <id=name> |
Monitor to show and its public name (repeatable) | - | No |
--json |
Output in JSON format | - | No |
status-pages show
Show a status page
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--id <id> |
Status page ID | - | Yes |
--json |
Output in JSON format | - | No |
status-pages update
Change the title, description or monitor selection
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--id <id> |
Status page ID | - | Yes |
-t, --title <title> |
Public page title | - | No |
-d, --description <text> |
Public description ("" clears it) | - | No |
-m, --monitor <id=name> |
Replace the selection; repeat for each monitor | - | No |
--clear-monitors |
Remove every monitor (drafts only) | - | 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.
- 4d ago First seen · 189 lines · 0 tokens per session scan A 4224b2cf09fd
status-pages 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,555 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-10-13.
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.