T08 · Insecure Dependencies
- Location
SKILL.md:76- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent test-generation helper, but its test execution and in-place mutation-testing guidance can alter project files without enough safeguards.
Install only if you are comfortable with a testing skill that may run project code and modify test or source files. Use a virtual environment, review generated changes before committing, and avoid mutation testing in your main working tree unless you have backups or a disposable worktree.
SKILL.md:76Unpinned Third-Party Dependency Installation
modules/quality-validation.md:218Mutation Testing Can Leave Source Files Corrupted After Interrupted Execution
Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.
### Verification Steps
1. **Run the test**: Must pass
2. **Check other tests**: All still passing
3. **No warnings/errors**: Clean execution
### REFACTOR Phase: Clean Up
The trigger phrase "testing" is extremely broad for an automatically invokable skill. In normal development conversations, this can cause the skill to activate in many unrelated contexts, increasing the chance that it influences workflows, runs analysis/generation steps, or steers the agent unexpectedly when the user did not explicitly request it.
The trigger phrase "code changes require new or updated test coverage" is ambiguous and policy-like rather than a precise invocation cue. Because it overlaps with common review language, the skill may activate based on routine discussion of code quality rather than an explicit request, leading to unintended execution paths or agent behavior changes.
This module explicitly describes executing tests via pytest and performing mutation testing by applying changes to source files and restoring them, but it provides no safety constraints, user confirmation requirements, sandboxing guidance, or warnings about code execution and file modification risks. In an agent skill, that is dangerous because tests and project code can contain attacker-controlled behavior, so blindly running them or mutating workspace files can trigger arbitrary code execution, side effects, or repository corruption.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
Then it must NOT find manipulative imperatives.
Imperative language causes Claude to ignore user intent
and force actions without consent.
"""
forbidden = [
"YOU MUST EXECUTE THIS NOW",
No suspicious patterns detected.