Command_Injection_Test
ListedTests system prompts for command injection vulnerabilities by attempting to execute arbitrary shell commands.
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 command_injection_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
This skill tests for command injection vulnerabilities in systems. It attempts to inject malicious commands into user inputs and observes the system's response, revealing potential security flaws. The skill is designed to identify weaknesses where untrusted data can be executed as shell commands.
When to use it
- Security Audits: Evaluate the robustness of web applications or APIs that process external input.
- Penetration Testing: Simulate an attacker's attempt to exploit command injection vulnerabilities.
- Development Validation: Verify that code changes designed to prevent command injection are effective.
- Automated Security Checks: Integrate into CI/CD pipelines for continuous vulnerability assessment.
Key capabilities
- Command Injection Attempt: Injects various malicious commands into input fields.
- Response Analysis: Analyzes the system's output to detect successful command execution.
- Vulnerability Identification: Flags potential command injection vulnerabilities based on observed behavior.
Example prompts
- "Test for command injection in the
/searchendpoint with the query 'test; ls -al'" - "Can you try injecting a command into the filename field? Try
file.txt; whoami." - "Check if the system allows execution of commands when I enter
<script>alert('xss')</script>in the comment box."
Tips & gotchas
The skill's effectiveness depends on the target system’s configuration and security measures. Ensure you have proper authorization before using this skill, as unauthorized testing can be illegal or violate terms of service.