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 skills/gotempsh/temps/add-custom-domainnpx skills add gotempsh/temps --skill add-custom-domaingit 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/skills/gotempsh/temps/add-custom-domain)<a href="https://agentmods.dev/skills/gotempsh/temps/add-custom-domain"><img src="https://agentmods.dev/badge/skills/gotempsh/temps/add-custom-domain.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.00153 | $0.00998 |
| Opus 5 | $0.00077 | $0.00499 |
| Sonnet 5 | $0.00031 | $0.00200 |
| Haiku 4.5 | $0.00015 | $0.00100 |
Grade A, and why
add-custom-domain 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 6d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a Custom Domain
Add a custom domain to a Temps project and get automatic HTTPS. This skill drives the whole flow from the CLI; the human equivalent is Project → Domains → Add Domain in the dashboard.
When to use
The user wants their own domain (e.g. app.example.com) serving a Temps project,
with an SSL certificate, instead of the auto-assigned subdomain.
Prerequisites
- The Temps CLI is authenticated. Verify, and log in to the user's instance if needed
(
loginis a top-level command; the instance URL is the positional argument):bunx @temps-sdk/cli whoami || bunx @temps-sdk/cli login "<instance_url>" - The user knows the domain to add and which project it belongs to.
- The user can edit DNS for the domain (or has a DNS provider connected in Temps for DNS-01 / wildcard).
Steps
-
Identify the project. If the user gave a name but not an ID, list projects and resolve it:
bunx @temps-sdk/cli projects list --jsonNote the numeric
idof the target project. Use it as<project-id>below. -
Create the DNS record at the user's DNS provider so the domain points at the Temps server. Tell the user exactly what to add (you cannot create this for them unless a DNS provider is connected in Temps):
- Subdomain (
app.example.com):Arecord, nameapp, value = the server's public IP. ACNAMEto the server hostname also works. - Apex (
example.com):Arecord, name@, value = the server's IP. (CNAMEs are not allowed at the zone root.) - If the user is on Cloudflare, have them set the record to DNS only (grey cloud) during issuance so Temps' Let's Encrypt challenge isn't proxied.
- Subdomain (
-
Add the domain to the project. Default is the HTTP-01 challenge, handled automatically:
bunx @temps-sdk/cli custom-domains create --project-id <project-id> -d app.example.com -y- Apex + Cloudflare/another provider connected, or port 80 not reachable: use DNS-01 instead (see Wildcard below) — confirm a DNS provider is connected in Settings → DNS Providers first.
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.
- 6d ago First seen · 88 lines · 153 tokens per session scan A 2ecf31d34e9f
add-custom-domain is a skill published in the GitHub repository gotempsh/temps (713 stars, last pushed today), licensed Apache-2.0. It adds 153 tokens to every session and 998 once invoked, about $0.0008 per session on Opus 5. 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 skills, from other repositories
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
add-ci-area
Add a new project area to CI workflows.
ci-status
Check the CI pipeline status for the current branch after pushing changes. Reports pass/fail with failure details. Use this after every push to confirm your changes are truly done — CI must be green. TRIGGER when: after git push, after committing changes, when asked to check CI, or when verifying that work is complete.
deployment
Use when taking an app from source to live: choosing the deploy target from requirements (Hetzner+Coolify vs Vercel vs a third), then wiring container → CI → registry → host with build secrets, healthchecks and rollback. NOT one platform's mechanics (that is coolify, vercel, railway, render), NOT the Dockerfile alone…
ci-cd
· Write/review CI/CD for GitHub Actions, GitLab, Forgejo/Gitea, Woodpecker. Triggers: 'ci/cd', 'pipeline', 'github actions', 'gitlab ci', 'runner', 'renovate', 'trivy'. Not for git workflows (use git).
gitlab_pages_ci
GitLab CI — test job and GitLab Pages job (artifact public/); .gitlab-ci.yml templates.