adguardControl AdGuard Home DNS filtering via HTTP API. Use when managing blocklists/allowlists, checking domain filtering status, toggling protection, or clearing DNS cache. Supports blocking/allowing domains, viewing statistics, and protecting/disabling DNS filtering.
Install via ClawdBot CLI:
clawdbot install rowbotik/adguardManage AdGuard Home DNS filtering from the command line via the REST API.
curl installed (usually default on macOS/Linux)# Set password once
export ADGUARD_PASSWORD=your_admin_password
# Use commands
./adguard.sh status
./adguard.sh check example.com
./adguard.sh allow broken-site.com
./adguard.sh block malware.ru
Set environment variables for your AdGuard instance:
export ADGUARD_URL="http://192.168.1.100:3000" # Your AdGuard IP and port
export ADGUARD_USERNAME="admin" # Usually 'admin' (default)
export ADGUARD_PASSWORD="your_admin_password" # REQUIRED
Add to ~/.bashrc or ~/.zshrc for persistence.
Create ~/.adguard/config.json (optional):
{
"url": "http://192.168.1.100:3000",
"username": "admin"
}
Then set ADGUARD_PASSWORD separately for security.
Check if a domain is currently blocked or allowed.
./adguard.sh check doubleclick.net
# β doubleclick.net IS BLOCKED
# Blocked by: Adblock Plus filter
./adguard.sh check example.com
# β example.com is NOT blocked (allowed)
| whitelist Add a domain to the allowlist (whitelist). Creates an exception rule that overrides blocklists.
./adguard.sh allow broken-site.com
# β Added rule: @@||broken-site.com^
# Domain: broken-site.com
# Action: allow
| blacklist Add a domain to the blocklist. Creates a custom blocking rule.
./adguard.sh block spyware-domain.ru
# β Added rule: ||spyware-domain.ru^
# Domain: spyware-domain.ru
# Action: block
Display DNS filtering statistics and protection state.
./adguard.sh status
# βββββββββββββββββββββββββββββββ
# AdGuard Home Status
# βββββββββββββββββββββββββββββββ
# Protection: β ENABLED
#
# DNS Queries: 1,234
# Blocked by rules: 156
# Blocked by safe browsing: 23
# Safe search replacements: 5
# Block rate: 14%
# βββββββββββββββββββββββββββββββ
Enable or disable DNS protection. Useful for temporarily disabling filtering.
./adguard.sh toggle
# Disabling protection...
# β Protection is now false
Clear the DNS cache to apply rule changes immediately.
./adguard.sh cache-clear
# Clearing DNS cache...
# β Cache cleared
If you don't know your AdGuard URL:
nmap or check "Connected Devices"http://localhost:3000http://adguard-home.local:3000 (depends on network)AdGuard uses a DNS filtering rule syntax:
| Rule | Effect |
|------|--------|
| \|\|example.com^ | Block example.com and subdomains |
| @@\|\|example.com^ | Allow example.com (exception/whitelist) |
| example.com | Block exact domain only |
| \|\|ad.example.com^ | Block only ad.example.com |
See API Reference for complete syntax.
adguard.sh allow my-bank.com
adguard.sh block malicious-tracker.xyz
adguard.sh check ads.google.com
adguard.sh status
adguard.sh toggle
Error: Failed to authenticate
β Check ADGUARD_PASSWORD is correct and set
β Verify ADGUARD_URL points to the right IP and port
Error: API call failed (HTTP 401)
β Authentication failed, check credentials
Rules don't take effect
β Run adguard.sh cache-clear to flush DNS cache
β Wait 5+ minutes for clients to refresh their cache
β Restart your device's network connection
Can't connect to AdGuard
β Verify device is on the same network
β Check firewall isn't blocking port 3000
β Ping the device: ping
Block multiple domains:
for domain in tracker1.com tracker2.com tracker3.com; do
adguard.sh block "$domain"
done
Check multiple domains:
for domain in example.com test.org my-site.net; do
echo "Checking $domain..."
adguard.sh check "$domain"
done
See references/api.md for complete AdGuard Home API documentation.
Generated Mar 1, 2026
Home users can manage DNS filtering to block ads, trackers, and malware across all devices on their network. This skill allows them to quickly check domain status, add exceptions for trusted sites, and toggle protection for troubleshooting without accessing the AdGuard web interface.
IT administrators in small offices use this skill to enforce network policies by blocking distracting or unsafe websites. They can batch block domains, monitor filtering statistics, and clear DNS caches to ensure immediate rule application, enhancing productivity and security.
Parents configure AdGuard Home to restrict access to inappropriate content for children's devices. They can allow educational sites, block gaming or social media domains during study hours, and use the status command to review daily blocking activity.
Web developers test their applications by simulating blocked domains to ensure functionality under ad-blocking conditions. They can temporarily disable protection to isolate issues and use the check command to verify domain filtering status during development cycles.
Security professionals monitor network traffic by blocking known malicious domains and analyzing statistics for threats. They can quickly add new block rules in response to alerts and use cache clearing to enforce changes, aiding in incident response.
Offer this skill as a free command-line tool to attract users, then upsell premium features like automated batch operations, advanced analytics dashboards, or API integrations with other security platforms. Revenue comes from subscription fees for enhanced functionality.
IT service providers bundle this skill with their managed network security packages for small businesses. They charge monthly fees for setup, configuration, and ongoing management, using the skill to efficiently handle client DNS filtering needs remotely.
Sell pre-configured hardware devices like Raspberry Pi units with AdGuard Home and this skill installed. Include support and updates as part of the purchase, targeting home users and small offices seeking plug-and-play network security solutions.
π¬ Integration Tip
Ensure environment variables are set correctly in shell profiles for persistence, and use the config file option for non-sensitive settings to streamline deployment across multiple systems.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
Perform a comprehensive read-only security audit of Clawdbot's own configuration. This is a knowledge-based skill that teaches Clawdbot to identify hardening opportunities across the system. Use when user asks to "run security check", "audit clawdbot", "check security hardening", or "what vulnerabilities does my Clawdbot have". This skill uses Clawdbot's internal capabilities and file system access to inspect configuration, detect misconfigurations, and recommend remediations. It is designed to be extensible - new checks can be added by updating this skill's knowledge.
Use when reviewing code for security vulnerabilities, implementing authentication flows, auditing OWASP Top 10, configuring CORS/CSP headers, handling secrets, input validation, SQL injection prevention, XSS protection, or any security-related code review.
Security check for ClawHub skills powered by Koi. Query the Clawdex API before installing any skill to verify it's safe.
Scan Clawdbot and MCP skills for malware, spyware, crypto-miners, and malicious code patterns before you install them. Security audit tool that detects data exfiltration, system modification attempts, backdoors, and obfuscation techniques.