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/unitoneai/securityskills/dns-securitynpx skills add UnitOneAI/SecuritySkills --skill dns-securitygit clone --depth 1 https://github.com/UnitOneAI/SecuritySkillsWrote 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/unitoneai/securityskills/dns-security)<a href="https://agentmods.dev/skills/unitoneai/securityskills/dns-security"><img src="https://agentmods.dev/badge/skills/unitoneai/securityskills/dns-security.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.00092 | $0.04484 |
| Opus 5 | $0.00046 | $0.02242 |
| Sonnet 5 | $0.00018 | $0.00897 |
| Haiku 4.5 | $0.00009 | $0.00448 |
Grade A, and why
dns-security 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 — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DNS Security Review
A structured, repeatable process for evaluating DNS security posture against NIST SP 800-81 Rev 2 (Secure Domain Name System Deployment Guide) and CIS Controls v8 Control 9.2 (Use DNS Filtering Services). This skill covers DNSSEC deployment, encrypted DNS transport, Response Policy Zones, DNS exfiltration detection, and protective DNS services. All findings are mapped to framework controls with severity ratings and actionable remediation.
When to Use
If a target is provided via arguments, focus the review on: $ARGUMENTS
- DNS infrastructure security review as part of network security assessment.
- DNSSEC deployment readiness evaluation or post-deployment validation.
- Investigation of suspected DNS-based data exfiltration or command-and-control.
- Compliance audits requiring NIST SP 800-81 alignment.
- Protective DNS service evaluation or deployment planning.
- Incident response when DNS tunneling is suspected.
Context
DNS is a foundational protocol that is often under-secured. NIST SP 800-81 Rev 2 Section 2 identifies three primary DNS threat categories: DNS cache poisoning, DNS-based denial of service, and unauthorized zone data modification. DNSSEC addresses data integrity but not confidentiality. CIS Controls v8 Control 9.2 requires the use of DNS filtering services to block access to known malicious domains. Beyond these baseline controls, DNS is increasingly exploited as a covert data exfiltration channel because port 53 is almost universally permitted through firewalls. Detecting DNS tunneling and exfiltration requires analysis of query patterns, payload sizes, and entropy -- not just domain reputation.
Process
Step 1: Discovery -- Locate DNS Configurations
Use Glob and Grep to locate DNS server configurations, resolver settings, and related infrastructure definitions.
Patterns to search:
# BIND / named
**/named.conf*
**/named/*.zone
**/bind/**
**/zones/**
# Systemd-resolved / resolvconf
**/resolved.conf
**/resolv.conf
**/resolvconf/**
# Cloud DNS
**/*.tf # Terraform (aws_route53_zone, google_dns_managed_zone, azurerm_dns_zone)
**/dns*
**/route53*
# CoreDNS (Kubernetes)
**/Corefile
**/coredns*
# Pi-hole / AdGuard / RPZ
**/pihole*
**/adguard*
**/*.rpz
**/rpz*
# Application-level DNS settings
**/dnsconfig*
**/unbound*
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 · 427 lines · 92 tokens per session scan A 3bf9f8e2881c
dns-security is a skill published in the GitHub repository UnitOneAI/SecuritySkills (58 stars, last pushed 2mo ago), licensed MIT. It adds 92 tokens to every session and 4,484 once invoked, about $0.0005 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
analyzing-dns-logs-for-exfiltration
Analyzes DNS query logs to detect data exfiltration via DNS tunneling, DGA domain communication, and covert C2 channels using entropy analysis, query volume anomalies, and subdomain length detection in SIEM platforms. Use when SOC teams need to identify DNS-based threats that bypass traditional network security…
analyzing-network-flow-data-with-netflow
Parse NetFlow v9 and IPFIX records to detect volumetric anomalies, port scanning, data exfiltration, and C2 beaconing patterns. Uses the Python netflow library to decode flow records, builds traffic baselines, and applies statistical analysis to identify flows with abnormal byte counts, connection durations, and…
hunting-dns-tunneling-and-exfiltration
Detects DNS-based tunneling and data exfiltration in DNS logs: scoring high query volume to single domains, long/high-entropy subdomains, unusual record types, and encoded payload labels. Activates for requests to hunt DNS tunneling, detect DNS exfiltration, or analyze suspicious DNS query patterns.
analyzing-dns-logs-for-exfiltration
Analyzes DNS query logs to detect data exfiltration via DNS tunneling, DGA domain communication, and covert C2 channels using entropy analysis, query volume anomalies, and subdomain length detection in SIEM platforms. Use when SOC teams need to identify DNS-based threats that bypass traditional network security…
cis-aws-foundations-4.1
Ensure CloudTrail is enabled in all regions.
cis-aws-foundations-4.3
Ensure AWS Config is enabled in all regions.