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/dns-providergit 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/dns-provider)<a href="https://agentmods.dev/commands/gotempsh/temps/dns-provider"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/dns-provider.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 | $0.00000 | $0.01629 |
| Opus 5 | $0.00000 | $0.00814 |
| Sonnet 5 | $0.00000 | $0.00326 |
| Haiku 4.5 | $0.00000 | $0.00163 |
Grade A, and why
dns-provider 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 4d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dns-provider command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
dns-provider (alias: dnsp)
Manage DNS providers and managed domains
Subcommands:
list(ls) - List all DNS providerscreate(add) - Create a new DNS providershow- Show DNS provider detailsupdate- Update a DNS providerremove(rm) - Delete a DNS providertest- Test DNS provider connectionzones- List DNS zones for a providerdomains- Manage domains associated with a DNS providerlookup- Lookup DNS A records for a domain
dns-provider list (alias: ls)
List all DNS providers
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--json |
Output in JSON format | - | No |
dns-provider create (alias: add)
Create a new DNS provider
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-n, --name <name> |
Provider name | - | No |
-t, --type <type> |
Provider type (cloudflare, route53, digitalocean, namecheap, gcp, azure, manual, pebble) | - | No |
-d, --description <description> |
Provider description | - | No |
--api-token <token> |
API token (Cloudflare, DigitalOcean) | - | No |
--account-id <id> |
Cloudflare account ID (optional) | - | No |
--access-key-id <key> |
AWS access key ID | - | No |
--secret-access-key <secret> |
AWS secret access key | - | No |
--region <region> |
AWS region | - | No |
--api-user <user> |
Namecheap API user | - | No |
--api-key <key> |
Namecheap API key | - | No |
--username <username> |
Namecheap username | - | No |
--client-ip <ip> |
Namecheap whitelisted client IP | - | No |
--project-id <id> |
GCP project ID | - | No |
--service-account-email <email> |
GCP service account email | - | No |
--private-key-id <id> |
GCP private key ID | - | No |
--private-key <key> |
GCP private key | - | No |
--tenant-id <id> |
Azure tenant ID | - | No |
--client-id <id> |
Azure client ID | - | No |
--client-secret <secret> |
Azure client secret | - | No |
--subscription-id <id> |
Azure subscription ID | - | No |
--resource-group <name> |
Azure resource group | - | No |
--management-url <url> |
pebble-challtestsrv management API URL (local ACME test server only) | - | 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.
- 4d ago First seen · 191 lines · 0 tokens per session scan A 699f23f355e9
dns-provider 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 1,629 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-08-30.
Other commands, from other repositories
ci-status
Real-time GitHub Actions workflow status and recent runs.
pipeline-generate
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with pipeline generate in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
rollback-plan
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with rollback plan in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
secrets-audit
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with secrets audit in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
pipeline-generate
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with pipeline generate in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
pipeline-generate
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with pipeline generate in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.