Official agent skill

Run DNS Server

by hashicorp in hashicorp/terraform-provider-dns

Guide for running a local containerized DNS server. An agent skill from hashicorp/terraform-provider-dns.

OfficialMPL-2.0Auto-check passedDevOps & Cloud

Install Run DNS Server

skills CLI

$ npx skills add hashicorp/terraform-provider-dns --skill run-dns-server -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install hashicorp/terraform-provider-dns run-dns-server --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/hashicorp/terraform-provider-dns.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/run-dns-server .claude/skills/run-dns-server && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "run-dns-server" agent skill from https://github.com/hashicorp/terraform-provider-dns/tree/main/.github/skills/run-dns-server into .claude/skills/run-dns-server/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-dns-server", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/hashicorp/terraform-provider-dns/tree/main/.github/skills/run-dns-server

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add hashicorp/terraform-provider-dns --skill run-dns-server -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install hashicorp/terraform-provider-dns run-dns-server --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hashicorp/terraform-provider-dns.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/run-dns-server .agents/skills/run-dns-server && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "run-dns-server" agent skill from https://github.com/hashicorp/terraform-provider-dns/tree/main/.github/skills/run-dns-server into .agents/skills/run-dns-server/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-dns-server", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add hashicorp/terraform-provider-dns --skill run-dns-server -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install hashicorp/terraform-provider-dns run-dns-server --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hashicorp/terraform-provider-dns.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/run-dns-server .cursor/skills/run-dns-server && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "run-dns-server" agent skill from https://github.com/hashicorp/terraform-provider-dns/tree/main/.github/skills/run-dns-server into .cursor/skills/run-dns-server/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-dns-server", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/hashicorp/terraform-provider-dns.git --path .github/skills/run-dns-server

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add hashicorp/terraform-provider-dns --skill run-dns-server -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install hashicorp/terraform-provider-dns run-dns-server --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hashicorp/terraform-provider-dns.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/run-dns-server .gemini/skills/run-dns-server && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "run-dns-server" agent skill from https://github.com/hashicorp/terraform-provider-dns/tree/main/.github/skills/run-dns-server into .gemini/skills/run-dns-server/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-dns-server", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install hashicorp/terraform-provider-dns run-dns-server

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add hashicorp/terraform-provider-dns --skill run-dns-server -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/hashicorp/terraform-provider-dns.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/run-dns-server .github/skills/run-dns-server && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "run-dns-server" agent skill from https://github.com/hashicorp/terraform-provider-dns/tree/main/.github/skills/run-dns-server into .github/skills/run-dns-server/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-dns-server", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add hashicorp/terraform-provider-dns --skill run-dns-server -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install hashicorp/terraform-provider-dns run-dns-server --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hashicorp/terraform-provider-dns.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/run-dns-server .opencode/skills/run-dns-server && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "run-dns-server" agent skill from https://github.com/hashicorp/terraform-provider-dns/tree/main/.github/skills/run-dns-server into .opencode/skills/run-dns-server/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-dns-server", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: run-dns-server
GitHub stars: 149
Token cost: ~352 tokens
SKILL.md length: 59 words
Files: 1
Skills in repo: 1
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MPL-2.0

At a glance

Guide for running a local containerized DNS server. An agent skill from hashicorp/terraform-provider-dns.

Works in 2 steps: Check whether the DNS server is already… → If the DNS server is not already alive,…
Tasks that involve End-to-end testing
Calls docker
Tasks that involve Infrastructure as code

What it does

Run DNS Server is an agent skill from hashicorp/terraform-provider-dns, published by the product's own GitHub organization. Guide for running a local containerized DNS server. Use this when asked to run an acceptance test or to run a test with the prefix TestAcc.

Its SKILL.md is about 350 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering End-to-end testing and Infrastructure as code. It works with Terraform. The repository describes itself as: Utility provider that supports DNS updates (RFC 2136) and can optionally be configured with secret key based transaction authentication (RFC 2845). The licence is MPL-2.0.

When your agent uses it

Tasks that involve End-to-end testing
Tasks that involve Infrastructure as code

Example prompts

“/run-dns-server”

Requirements

Docker

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

Check whether the DNS server is already alive by querying its locally-mapped port
If the DNS server is not already alive, then start the DNS server by running this command in the background

What it can do on your machine

Read from SKILL.md and the folder at commit b3e1225. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- docker
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use docker, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Run DNS Server loads about 352 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 59 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~39
When it runs · the whole SKILL.md, loaded when a task matches: ~352

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashicorp/terraform-provider-dns at commit b3e1225, republished under its MPL-2.0 licence (© hashicorp). 59 words, ~352 tokens.

Download SKILL.mdSave it as .claude/skills/run-dns-server/SKILL.md (or your agent's skills folder).

name: run-dns-server
description: Guide for running a local containerized DNS server. Use this when asked to run an acceptance test or to run a test with the prefix `TestAcc`.

Before running any acceptance tests for the DNS provider, start a DNS server:

Check whether the DNS server is already alive by querying its locally-mapped port:
```
dig @127.0.0.1 -p 15353 +short ns.example.com
```
Expected command output is "127.0.0.1."

If the DNS server is not already alive, then start the DNS server by running this command in the background:

docker run --privileged --cgroupns=host -d --tmpfs /tmp --tmpfs /run \
 -v /sys/fs/cgroup:/sys/fs/cgroup:rw \
 -v /etc/localtime:/etc/localtime:ro \
 -v $PWD/internal/provider/testdata/named.conf.kerberos:/etc/named.conf:ro \
 -p 127.0.0.1:15353:53 \
 -p 127.0.0.1:15353:53/udp \
 --rm --name ns --hostname ns.example.com ns

After starting the DNS server, verify that the DNS server is alive by querying its locally-mapped port:
```
dig @127.0.0.1 -p 15353 +short ns.example.com
```
Expected command output is "127.0.0.1." Display no output unless there is a problem.
If there is a problem, do not run the acceptance tests.

Add these environment variables to all go test commands for acceptance tests in the DNS provider:

DNS_UPDATE_SERVER=127.0.0.1
DNS_UPDATE_PORT=15353

Files

Just SKILL.md in .github/skills/run-dns-server of hashicorp/terraform-provider-dns.

Open the folder on GitHubat commit b3e1225

Compare with similar skills

Run DNS Server next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Run DNS Server compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Run DNS Server this skillhashicorp/terraform-provider-dns	149	—	~352	Automated safety check: Pass	MPL-2.0	today
Dev OverridesGoogleCloudPlatform/magic-modules	974	—	~432	Automated safety check: Pass	Custom licence	today
Terraform Provider Developmentshepherdjerred/monorepo	112	—	~1.2k	Automated safety check: Pass	MPL-2.0	today
Smt E2E Dataflow DebuggingGoogleCloudPlatform/DataflowTemplates	1.3k	—	~1.8k	Automated safety check: Pass	Apache-2.0	today
Avm Tf TestingAzure/terraform-azurerm-avm-ptn-alz	135	—	~1.8k	Automated safety check: Pass	MIT	2 days ago
Schema Coverageelastic/terraform-provider-elasticstack	210	—	~1.4k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Dev Overrides
GoogleCloudPlatform/magic-modules
Configures Terraform CLI with developer overrides to test locally built provider binaries without full Go acceptance tests, enabling rapid plan/apply cycles.
974 GitHub stars~432 tokensUpdated today
DevOps & CloudAuto-check passed
Terraform Provider Development
shepherdjerred/monorepo
Build, extend, test, document, and migrate Terraform providers with the Plugin Framework.
112 GitHub stars~1.2k tokensUpdated today
DevOps & CloudAuto-check passed
Smt E2E Dataflow Debugging
GoogleCloudPlatform/DataflowTemplates
Debugs logical errors and data discrepancies in Dataflow templates by launching jobs via Terraform and comparing source (e.g.
1.3k GitHub stars~1.8k tokensUpdated today
DevelopmentAuto-check passed
Avm Tf Testing
Azure/terraform-azurerm-avm-ptn-alz
Official
A skill your agent uses for AVM Terraform validation, provider-mocked unit tests, real-Azure integration tests, E2E example tests, PowerShell hooks, OIDC, policy checks, and Avm.Authoring CI behavior.
135 GitHub stars~1.8k tokensUpdated 2 days ago
Testing & QAAuto-check passed
Schema Coverage
elastic/terraform-provider-elasticstack
Official
Analyzes a Terraform resource schema and compares it to attributes used in the acceptance test suite (configs + assertions).
210 GitHub stars~1.4k tokensUpdated today
Testing & QAAuto-check passed
Test Fix Workflow
GoogleCloudPlatform/magic-modules
Workflow for diagnosing, fixing, and verifying failing Terraform acceptance tests from GitHub issue URLs (detecting test-failure labels), direct prompts, or log files using Failure Scenario Decision…
974 GitHub stars~1.3k tokensUpdated today
Testing & QAAuto-check passed

Works with

Terraform

Questions about Run DNS Server

What does Run DNS Server do?

Guide for running a local containerized DNS server. An agent skill from hashicorp/terraform-provider-dns. Run DNS Server is an agent skill from hashicorp/terraform-provider-dns, published by the product's own GitHub organization. Guide for running a local containerized DNS server.

When should I use Run DNS Server?

Run DNS Server fits situations like: tasks that involve End-to-end testing; tasks that involve Infrastructure as code.

How do I install Run DNS Server in Claude Code?

Run `npx skills add hashicorp/terraform-provider-dns --skill run-dns-server -a claude-code`. Or copy the skill folder (.github/skills/run-dns-server in hashicorp/terraform-provider-dns) into .claude/skills/run-dns-server in your project. Claude Code loads it when a task matches its description.

How do I install Run DNS Server in Codex?

Run `npx skills add hashicorp/terraform-provider-dns --skill run-dns-server -a codex`. Or copy the skill folder (.github/skills/run-dns-server in hashicorp/terraform-provider-dns) into .agents/skills/run-dns-server in your project. Codex loads it when a task matches its description.

Can I use Run DNS Server in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashicorp/terraform-provider-dns --skill run-dns-server -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-dns-server, .gemini/skills/run-dns-server, .github/skills/run-dns-server and .opencode/skills/run-dns-server in your project.

What does Run DNS Server need to run?

Going by SKILL.md and its folder, Run DNS Server needs the command-line tools its instructions call (docker). Our summary lists: Docker.

Does Run DNS Server access the network?

SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Run DNS Server safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Run DNS Server use?

Run DNS Server is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Run DNS Server use?

About 352 tokens (SKILL.md is roughly 1.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Run DNS Server?

Skills that share tags, products or a category with Run DNS Server: Dev Overrides (GoogleCloudPlatform/magic-modules, 974 stars), Terraform Provider Development (shepherdjerred/monorepo, 112 stars), Smt E2E Dataflow Debugging (GoogleCloudPlatform/DataflowTemplates, 1.3k stars) and Avm Tf Testing (Azure/terraform-azurerm-avm-ptn-alz, 135 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run DNS Server?

hashicorp (a GitHub organization, an official publisher) maintains it in hashicorp/terraform-provider-dns, which has 149 GitHub stars. The repository was last updated on October 7, 2026.

Source: hashicorp/terraform-provider-dns on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Run DNS Server

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

Dev Overrides

Terraform Provider Development

Smt E2E Dataflow Debugging

Avm Tf Testing

Schema Coverage

Test Fix Workflow

Related

Questions about Run DNS Server