new-workspace
Pass
Audited by Gen Agent Trust Hub on Aug 22, 2026
Risk Level: SAFECOMMAND_EXECUTIONDATA_EXFILTRATION
Full Analysis
- [COMMAND_EXECUTION]: The skill instructions direct the agent to use user-supplied arguments (workspace name and target path) directly in shell commands such as
mkdirandcp. Without explicit instructions for the agent to sanitize or escape these strings, there is a risk of command injection if a user provides a workspace name containing shell metacharacters (e.g.,;,&&,|). - Evidence: The
mkdir -p <target-parent>/<workspace-name>andcp -r ... <target-parent>/<workspace-name>/commands in Step 4 depend on unsanitized user input from$ARGUMENTS. - [DATA_EXFILTRATION]: The skill is configured to default to creating public GitHub repositories via the
gh repo createcommand. This represents a data exposure risk, as identity facts extracted from~/.claude/CLAUDE.md(Step 3) are embedded into the workspace and subsequently published to the internet unless the user explicitly provides the--privateor--local-onlyflags. - Evidence: Step 7 instructions specify:
gh repo create <workspace-name> --<public|private> --source=. --push, where public is the default behavior stated in the arguments section. - [INDIRECT_PROMPT_INJECTION]: The skill processes untrusted external input and uses it to perform high-capability operations, creating a vulnerability surface for injection attacks.
- Ingestion points: User-supplied strings in
$ARGUMENTSand local identity/environment facts in~/.claude/CLAUDE.md(SKILL.md). - Boundary markers: None present; the instructions do not specify delimiters or warnings to ignore instructions embedded in the user-supplied strings.
- Capability inventory: The skill uses
mkdir,cp,git init/add/commit, andgh repo create(CLI tools with shell access). - Sanitization: Absent; there is no instruction to validate, filter, or escape the workspace name or path before passing them to the shell.
Audit Metadata