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/incidentsgit 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/incidents)<a href="https://agentmods.dev/commands/gotempsh/temps/incidents"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/incidents.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 | $0.00000 | $0.00827 |
| Opus 5 | $0.00000 | $0.00413 |
| Sonnet 5 | $0.00000 | $0.00165 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
incidents 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 3d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
incidents command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
incidents (alias: incident)
Manage incidents for status pages and monitoring
Subcommands:
list(ls) - List incidents for a projectcreate(add) - Create a new incidentshow- Show incident detailsupdate-status- Update an incident statusupdates- List status updates for an incidentbucketed- Get bucketed incident data for a project
incidents list (alias: ls)
List incidents for a project
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--project-id <id> |
Project ID | - | Yes |
--status <status> |
Filter by status (investigating, identified, monitoring, resolved) | - | No |
--environment-id <id> |
Filter by environment ID | - | No |
--page <n> |
Page number | - | No |
--page-size <n> |
Items per page | - | No |
--json |
Output in JSON format | - | No |
incidents create (alias: add)
Create a new incident
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--project-id <id> |
Project ID | - | Yes |
-t, --title <title> |
Incident title | - | No |
-d, --description <description> |
Incident description | - | No |
-s, --severity <severity> |
Severity level (critical, major, minor) | - | No |
-y, --yes |
Skip confirmation prompts (for automation) | - | No |
incidents show
Show incident details
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--id <id> |
Incident ID | - | Yes |
--json |
Output in JSON format | - | No |
incidents update-status
Update an incident status
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--id <id> |
Incident ID | - | Yes |
-s, --status <status> |
New status (investigating, identified, monitoring, resolved) | - | No |
-m, --message <message> |
Status update message | - | 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.
- 3d ago First seen · 97 lines · 0 tokens per session scan A d39defece214
incidents 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 827 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
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
monitor-ci
You are the orchestrator for monitoring Nx Cloud CI pipeline executions and handling self-healing fixes. You spawn the ci-monitor-subagent subagent to poll CI status and make decisions based on the results.
ci-health
Check all GitHub Actions workflows for failures, create P0 tickets, gate each ticket, and auto-fix safe failures.
router-on
Route Claude Code through the Weave Router again (turn it back on).
beta
Toggle beta HMM routing for this session.
cf-scaffold-project
Scaffold a Cloudflare project — Worker, Pages, or Worker+D1+R2 starter — with Wrangler config, Terraform skeleton, and GitHub Actions deploy using scoped API tokens.