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/otel)<a href="https://agentmods.dev/commands/gotempsh/temps/otel"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/otel/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/otel"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/otel.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.00388 |
| Opus 5.5 | $0.00000 | $0.00155 |
| Sonnet 5.5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
otel 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 1mo 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.
What it actually says
otel command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
otel
Inspect the OTLP ingest pipeline itself — throughput, drops and failure reasons (server-wide, not project-scoped; see "temps metrics" to query ingested application metrics)
Subcommands:
ingest-errors- Show why ingest batches were dropped, grouped by signal and failure reasonpipeline-history- Show pipeline counter trends over time (received/stored/dropped per signal)
otel ingest-errors
Show why ingest batches were dropped, grouped by signal and failure reason
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--limit <n> |
Max failure groups to return (default: 20, server cap: 100) | - | No |
--json |
Output in JSON format | - | No |
otel pipeline-history
Show pipeline counter trends over time (received/stored/dropped per signal)
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--period <period> |
Time period: 1h, 6h, 24h, 7d (server presets), or today/h/d resolved locally | 24h |
No |
--start-time <iso> |
Explicit window start (RFC 3339) — overrides --period | - | No |
--end-time <iso> |
Explicit window end (RFC 3339) — overrides --period | - | 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.
- 1mo ago First seen · 39 lines · 0 tokens per session scan A 3a0cd103e449
otel is a command published in the GitHub repository gotempsh/temps (874 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 388 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
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.
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.
fix-ci-issue
Pick up one CI-failure task (source:ci), fix the failing lint/test, and push — retried at most 3 times.