pr-naming
Fail
Audited by Gen Agent Trust Hub on Sep 1, 2026
Risk Level: HIGHCOMMAND_EXECUTIONDYNAMIC_EXECUTIONCREDENTIALS_UNSAFEINDIRECT_PROMPT_INJECTION
Full Analysis
- [COMMAND_EXECUTION]: The script
scripts/check_pr.pyis vulnerable to command injection in thecheck_branchfunction. It takes thebranch_nameargument directly from command-line input and interpolates it into a shell command string executed viasubprocess.run(shell=True). This allows an attacker to execute arbitrary commands by providing a crafted branch name containing shell metacharacters like semicolons or pipes.\n- [DYNAMIC_EXECUTION]: Thecheck_titlefunction inscripts/check_pr.pyuses theeval()function to compile a regular expression. The use ofeval()for code execution is a dangerous practice that can be exploited if the pattern string is ever influenced by external data.\n- [CREDENTIALS_UNSAFE]: The documentation fileSKILL.mdcontains a hardcoded GitHub Personal Access Token (ghp_test0000000000000000000000000000000000) in its usage examples. While this token appears to be a dummy value for testing, hardcoding credential patterns in documentation encourages unsafe security practices.\n- [INDIRECT_PROMPT_INJECTION]: The skill provides an attack surface for indirect prompt injection as it processes external inputs (PR titles and branch names) through functions with execution capabilities.\n - Ingestion points: Data enters via command-line arguments in
scripts/check_pr.py.\n - Boundary markers: None are present to distinguish data from instructions.\n
- Capability inventory: The skill uses
subprocess.run(shell execution) andeval(dynamic code execution).\n - Sanitization: No sanitization or validation is applied to inputs before execution.
Recommendations
- AI detected serious security threats
Audit Metadata