sc-cmdi

Detect OS command injection in shell execution and subprocess calls.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kocakburhan/emlakdefter --skill sc-cmdi-kocakburhan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc-cmdi
Source: https://github.com/kocakburhan/emlakdefter/tree/main/.agents/skills/security-check/skills/sc-cmdi
Command: npx skills add https://github.com/kocakburhan/emlakdefter --skill sc-cmdi-kocakburhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects OS command injection vulnerabilities in code that uses shell execution, subprocess calls, or process spawning, distinguishing between full command injection and argument injection.

Core Features & Use Cases

  • Cross-language coverage detects risky command execution patterns in Python, JavaScript/Node.js, Go, PHP, Java, C#, and Ruby.
  • Phase-based discovery and verification to identify command vs argument injection with actionable findings.
  • Integrates into code reviews and CI checks to surface vulnerabilities early and provide remediation guidance.

Quick Start

Scan your codebase for risky command executions and report vulnerable patterns.

Frequently Asked Questions about sc-cmdi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect OS command injection vulnerabilities in multi-language codebases?

You can detect OS command injection vulnerabilities by running static analysis across multi-language codebases to identify risky shell execution, subprocess calls, and process spawning patterns with structured remediation guidance.

What is the difference between command injection and argument injection in subprocess calls?

Command injection exploits shell execution to run arbitrary commands, while argument injection manipulates process spawning parameters. This Skill uses phase-based discovery and verification to distinguish between full command and argument injection during security reviews.

Can I use static analysis to find shell execution vulnerabilities in Python and Node.js?

Yes, cross-language coverage detects risky command execution patterns in Python, JavaScript/Node.js, Go, PHP, Java, C#, and Ruby by scanning subprocess calls and process spawning during static analysis.

How do I integrate command injection detection into automated CI checks?

You can integrate command injection detection into automated CI checks by running static analysis to surface vulnerabilities early during code reviews, ensuring risky shell execution patterns are caught before deployment.

What's the best way to scan codebases for risky subprocess calls and process spawning?

The best way to scan codebases for risky subprocess calls is using phase-based discovery and verification that identifies vulnerable patterns in shell execution and provides clear findings for command and argument injection.