Claude's IP privacy.
Inspect every layer.

This article provides Aegis Network Privacy Skill 1.0.0, published on 2026-10-29. ZIP size is 25,603 bytes, containing 9 files: skill description, agent configuration, usage reference, and four PowerShell scripts.

Verify the SHA-256 hash in PowerShell after downloading. Replace the path in the command with your actual download location:

Get-FileHash -LiteralPath 'C:\Users\你的用户名\Downloads\aegis-network-privacy-skill.zip' -Algorithm SHA256

SHA-256：
55c3b0cbb57346dbe54ff79a1f742a65b8550847f194aedcce65e3502c2403f5

The hash confirms that your download matches the original package hosted here.

Applicable environment:Windows 10 / 11 x64、Windows PowerShell 5.1. Use local support SKILL.md AI client with Windows command execution; diagnostic scripts can be run independently without the need to install Aegis desktop software.

1. Extract All ZIP Contents

   get aegis-network-privacy Folder, you can see it directly after opening it SKILL.md、agents、references and scripts。

2. Place It in Your Skills Directory

   The default location of the Codex is the current user's ~/.codex/skills/. set CODEX_HOME When using the skills/. will the entire aegis-network-privacy Put the folder in it. If there is a skill with the same name, keep it first and check the original version.

3. Refresh Your AI Client

   Refresh the skill list or reopen the client to confirm that it appears in the list aegis-network-privacy. Other AI clients are installed from their local skills directory, retaining the same file structure.

skills/
  aegis-network-privacy/
    SKILL.md
    agents/openai.yaml
    references/
    scripts/

Send the prompt below in the AI client where you installed the skill. Keep your existing VPN and proxy running. Inspect local information sources and existing application-rule coverage for Claude's current executable path.

Use $aegis-network-privacy to investigate real-IP exposure risks when using Claude on my computer.
Start with local, read-only checks. Keep my existing VPN and proxy running, and do not sign in to any account.
Identify Claude's current executable path and version, then inspect local IPv4 information sources and whether existing Aegis application firewall rules cover that path.
Assess local information readability, application-rule coverage and public egress separately. Do not send external requests by default.
Report sanitized evidence paths, coverage gaps and follow-up steps. Do not automatically modify any network configuration.

Six-Source IPv4 Audit

Inspect six IPv4 information sources: the native Windows address table, NetTCPIP addresses, routes, WMI, .NET network interfaces and TCP/IP registry fields. Produce sanitized results.

Claude Rule Coverage Checks

Identify Claude's current executable path and version, then check the existing Aegis.AppGuard.v1 rules for coverage of that path, physical network interfaces and effective configuration. List uncovered paths as gaps.

Post-Update Path Review

After a Claude update, locate the current executable and recheck its path, rules and network-interface scope. Plan follow-up work for the specific gaps found, keeping sanitized evidence from before and after the checks.

Local Reports

No external requests are sent by default. Reports omit raw IP addresses, hostnames, MAC addresses, full executable paths and network-interface aliases. Results are saved in new local files and should be read within the scope of the checks performed.

The standalone script is located at scripts/local-ip-surface.ps1 with scripts/inspect-guard.ps1; the other two copies test-*.ps1 For offline self-test. Review the script first, run it with client permissions, and follow the computer's existing script policy.