Network_Egress_Test
ListedVerifies network connectivity from within a simulated environment to external resources using configurable protocols.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add charpup/skill-security-auditor --skill network_egress_test -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
charpup
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 2 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
Declares what it does: failed
SKILL.md has no YAML frontmatter, so it declares nothing machine-readable.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: api.clawsec.io.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
api.clawsec.ioundeclaredraw.githubusercontent.comsource hostgithub.comsource hostWhat it found
- config/default.yaml:24contacts api.clawsec.io
feed_url: https://api.clawsec.io/v1/feed - lib/clawsec_integration.py:48contacts api.clawsec.io
"https://api.clawsec.io/v1/feed"
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned charpup/skill-security-auditor at 086718493c.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 086718493c
- Manifest
- SKILL.md
- Scanned
- 30 files, 3,341 lines
About this skill
What it does
The network_egress_test skill allows an AI agent to perform basic network connectivity tests from within a sandboxed environment. It can verify if the agent can reach specific external IP addresses and ports, simulating outbound network traffic. This is useful for confirming that egress rules are correctly configured and preventing unauthorized connections.
When to use it
- Security Auditing: Verify an AI agent's ability to connect to necessary services while ensuring adherence to security policies.
- Egress Rule Validation: Test the effectiveness of network egress rules by attempting connections to specific external resources.
- Troubleshooting Connectivity Issues: Diagnose problems with outbound network connectivity within a sandboxed environment before applying changes to production systems.
- Testing New Environments: Confirm that an AI agent can successfully connect to required services when deployed in a new or unfamiliar network environment.
Key capabilities
- Connects to specified IP addresses and ports.
- Simulates outbound network traffic within a sandbox.
- Verifies the functionality of egress rules.
Example prompts
- "Can you test if I can reach 8.8.8.8 on port 53?"
- "Perform an egress test to google.com on port 443."
- "Test network connectivity to 192.0.2.1 on port 80."
Tips & gotchas
The skill operates within a sandboxed environment; results may not perfectly reflect real-world network conditions. Ensure the sandbox has appropriate egress permissions configured for accurate testing.