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/logs)<a href="https://agentmods.dev/commands/gotempsh/temps/logs"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/logs/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/logs"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/logs.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.03003 |
| Opus 5.5 | $0.00000 | $0.01201 |
| Sonnet 5.5 | $0.00000 | $0.00601 |
| Haiku 4.5 | $0.00000 | $0.00300 |
Grade A, and why
logs 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
logs command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
logs (alias: glogs)
Search collected logs across every project and database you can access
Subcommands:
search- Search log lines across projects (newest first)facets- Distinct values and counts per field for the same filter scopeattributes- Attribute keys observed in the window, most common first (requires the ClickHouse line index)histogram- Line counts bucketed over time, optionally split by a label or attribute (requires the ClickHouse line index)aggregate- Group-by aggregation over lines (requires the ClickHouse line index)capabilities- Whether container logs are being collected, and whether attribute facets, histograms and aggregates are available
logs search
Search log lines across projects (newest first)
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--limit <n> |
Lines per request (default: 200, max: 1000) | - | No |
--cursor <token> |
Resume from a previous next_cursor | - | No |
--all |
Follow next_cursor automatically until the results run out (or --max-pages is reached, default 20 pages) | - | No |
--max-pages <n> |
Page ceiling for --all (default: 20) | - | No |
--since <duration> |
Relative window ending now, e.g. 30m, 6h, 7d (default: 1h) | - | No |
--start-time <iso> |
Window start (ISO 8601); overrides --since | - | No |
--end-time <iso> |
Window end (ISO 8601); defaults to now | - | No |
--source <kind> |
collected (default), application, or service | - | No |
| `--project <id | slug | name>` | Restrict to a project, repeatable |
| `--external-service <id | name>` | Restrict to a managed database/service, repeatable | `` |
--scope <kind:id> |
Explicit resource identity, e.g. application:12, repeatable | `` | No |
--level <level> |
TRACE|DEBUG|INFO|WARN|ERROR, repeatable | `` | No |
--env <name> |
Environment, repeatable | `` | No |
--service <name> |
Container service label (web, worker, …), repeatable | `` | No |
--container <id> |
Container ID, repeatable | `` | No |
--node <id> |
Worker node ID, repeatable | `` | No |
--deploy <id> |
Deployment ID | - | No |
--text <substring> |
Case-insensitive message substring match | - | No |
--attr <pred> |
Attribute predicate, repeatable: =, !=, ^=, >, <, or ? for "exists" (requires the ClickHouse line index) | `` | 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 Changed a25e89bc2b90
- 26d ago First seen · 168 lines · 0 tokens per session scan A d6c80ef0eba6
logs 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 3,003 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-22.
Other commands, from other repositories
incident-runbook
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with incident runbook in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
add-debug-wait
Add a wait step to a CI workflow for debugging test failures.
pr-quality-gate-reliability
You are reviewing a pull request for production survivability: how the change behaves when its dependencies misbehave, time out, or fail.
fix-ci
Find failing PR checks, inspect logs or check links, and apply focused fixes. Routing depends on failure type (build/test/security). Usage: /fix-ci [branch|PR].
drift-alert-issue
Detection Date: $DETECTIONDATE Workflow Run: $SERVERURL/$REPOSITORY/actions/runs/$RUNID.
resolve_pr_ci_failures
Triage and remediate PR CI failures; capture evidence and write an artifact.