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/tunnels)<a href="https://agentmods.dev/commands/gotempsh/temps/tunnels"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/tunnels/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/tunnels"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/tunnels.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.01168 |
| Opus 5.5 | $0.00000 | $0.00467 |
| Sonnet 5.5 | $0.00000 | $0.00234 |
| Haiku 4.5 | $0.00000 | $0.00117 |
Grade A, and why
tunnels 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 today.
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tunnels command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
tunnels
Ingress tunnels: publish apps on workers with no open ports or certificates. Apps under a tunnel's domain go live by adding the hostname to an environment
Subcommands:
list- List tunnels, what each publishes and the workers it runs onworkers- List worker nodes, for choosing where a tunnel runs (create --node)create- Create a tunnel for a managed zone and run it on workers. The zone must already be managed by the DNS provider (dns-providers domains add); workers must allow ingresshostnames- List hostnames tunnels publish or could publish, with their state and whyexplain- Explain how a hostname reaches visitors: which tunnel carries it, or why none doesroute- Choose how a hostname reaches visitors: through a tunnel (--tunnel ), whichever tunnel covers it (--automatic), or no tunnel (--off)publish- Set what a tunnel publishes: every app under its domain (--all) or only chosen hostnames (--chosen)nodes- Set the workers a tunnel runs on (an empty list stops it everywhere)links- Show a tunnel's live connections to the provider: data centre, age, workersync- Re-check a tunnel with its provider and recreate it if it was deleted there
tunnels list
List tunnels, what each publishes and the workers it runs on
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--page <page> |
Page number (1-indexed) | 1 |
No |
--page-size <pageSize> |
Items per page (max 100) | 20 |
No |
--json |
Output in JSON format | - | No |
tunnels workers
List worker nodes, for choosing where a tunnel runs (create --node)
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--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.
- today First seen · 128 lines · 0 tokens per session scan A 367e1ce7fe42
tunnels is a command published in the GitHub repository gotempsh/temps (864 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,168 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-23.
Other commands, from other repositories
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.
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.
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.
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.