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/settingsgit 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/settings)<a href="https://agentmods.dev/commands/gotempsh/temps/settings"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/settings.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.1 | $0.00000 | $0.00794 |
| Opus 5 | $0.00000 | $0.00397 |
| Sonnet 5 | $0.00000 | $0.00159 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
settings 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 2d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
settings command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
settings
Manage platform settings
Subcommands:
show(get) - Show current platform settingsupdate(set) - Update platform settingsset-external-url- Set the external URL for the platformset-preview-domain- Set the preview domain pattern
settings show (alias: get)
Show current platform settings
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--json |
Output in JSON format | - | No |
settings update (alias: set)
Update platform settings
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-s, --setting <setting> |
Setting to update (external_url, preview_domain, letsencrypt, rate_limiting, security_headers, screenshots) | - | No |
-v, --value <value> |
Value for the setting | - | No |
--external-url <url> |
External URL for the platform | - | No |
--preview-domain <domain> |
Preview domain pattern | - | No |
--letsencrypt-email <email> |
Let's Encrypt email | - | No |
--letsencrypt-mode <mode> |
Let's Encrypt mode (staging, production) | - | No |
--rate-limiting-enabled <enabled> |
Enable rate limiting (true/false) | - | No |
--rate-limiting-rpm <rpm> |
Requests per minute | - | No |
--screenshots-enabled <enabled> |
Enable screenshots (true/false) | - | No |
--max-request-timeout <seconds> |
Hard ceiling for all upstream request/idle timeouts, in seconds | - | No |
--default-http-timeout <seconds> |
Default timeout for regular HTTP requests, in seconds | - | No |
--default-sse-idle-timeout <seconds> |
Default idle timeout for SSE streams, in seconds | - | No |
--default-websocket-idle-timeout <seconds> |
Default idle timeout for WebSocket connections, in seconds | - | No |
--max-memory-limit-mb <mb> |
Ceiling on a project/environment memory limit override, in MB (0 = no ceiling) | - | No |
--max-concurrent-connections-ceiling <count> |
Ceiling on a project/environment concurrent-connection override (0 = no ceiling) | - | No |
--allow-unlimited-timeouts <enabled> |
Whether projects may set a timeout of 0, i.e. no timeout (true/false) | - | No |
--console-force-https <mode> |
Redirect the console host to HTTPS: auto (once a cert exists), always, or never | - | No |
-y, --yes |
Skip confirmation prompts (for automation) | - | 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.
- 2d ago First seen · 74 lines · 0 tokens per session scan A 2e0b37cc263f
settings 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 794 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
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.
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.
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.
pr-check
Run all local CI checks before creating a PR.